date:20220829

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

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

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

So I am a liar now. But this works:

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

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

Title:
  Video thumbnails fail to generate

Status in totem package in Ubuntu:
  New

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

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

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

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

  Passing the -l flag causes it to work fine.

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

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

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

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

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


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

[Desktop-packages] [Bug 1988100] Re: Video thumbnails fail to generate

** Summary changed:

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

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

Title:
  Video thumbnails fail to generate

Status in totem package in Ubuntu:
  New

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

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

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

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

  Passing the -l flag causes it to work fine.

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

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

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

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

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


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

[Desktop-packages] [Bug 1988100] Re: Video thumbnails fail to genetate

On second thoughts,

> Error creating thread: Resource temporarily unavailable

sounds like it would be related to RLIMIT_NPROC. Although it does not
explain why -l works. Perhaps the thumbnailer contains a thread leak
that is triggered by the 30 second limit, which -l avoids.

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

Title:
  Video thumbnails fail to genetate

Status in totem package in Ubuntu:
  New

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

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

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

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

  Passing the -l flag causes it to work fine.

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

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

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

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

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


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

[Desktop-packages] [Bug 1988100] Re: Video thumbnails fail to genetate

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

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

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

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

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

Title:
  Video thumbnails fail to genetate

Status in totem package in Ubuntu:
  New

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

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

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

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

  Passing the -l flag causes it to work fine.

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

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

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

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

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


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

[Desktop-packages] [Bug 1988100] Re: Video thumbnails fail to genetate

> OpenBLAS blas_thread_init: RLIMIT_NPROC 125184 current, 125184 max

Don't be alarmed by that. Those two limits are correct and normal per
https://manpages.ubuntu.com/manpages/jammy/man2/setrlimit.2.html and it
does not mean you actually have that many processes/threads right now.

To check for crashes, please:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

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

Title:
  Video thumbnails fail to genetate

Status in totem package in Ubuntu:
  New

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

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

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

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

  Passing the -l flag causes it to work fine.

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

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

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

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

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


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

[Desktop-packages] [Bug 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4603
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4603

** Changed in: gnome-shell
 Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3091 => 
gitlab.gnome.org/GNOME/gnome-shell/-/issues #4603

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

Title:
  Add support for top bars on all monitors to allow for multi-monitor
  support in primary extensions - apps-menu, places-menu, topbar, etc

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

Bug description:
  This issue will effectively be a regression in desktop usage once
  Ubuntu switches from Unity to Gnome Shell. Gnome Shell does not work
  well with multiple monitors unlike every other desktop environment
  except Budgie, which is switching away from GTK/Gnome to Qt with
  Budgie 11 due out in the next month or two.

  I reported it upstream last month but it does not appear to have much
  traction at the moment.

  https://bugzilla.gnome.org/show_bug.cgi?id=780078

  "
  It would be nice if the primary included gnome-shell extensions, eg apps-menu 
and places-menu (and by extension the topbar) supported multi-monitor similar 
to how the bottom bar 'window-list' currently does. This was easy to achieve on 
Gnome 2 and now via MATE (out of the box) but there does not appear to be any 
way to do this with Gnome 3. This also leads to there not being a way to do 
this via 'Gnome Classic'. Even Windows finally (in W10) does this better out of 
the box than Gnome 3.

  BTW - Intel has supported IGP triple head since Ivy Bridge (2012) so
  it is very cheap to deploy a triple head system (~ $200 for 3 1080p
  monitors). AMD supports up to quad head in their IGPs.

  This has been blocking me from moving to Gnome 3 since its release and I 
finally decided to write a bug report about it. I have had all multi-monitor 
systems since prior to 2004.
  "

  And see comments #11 and #14 from Florian.

  "
  No, you don't want that in the extensions. Each extension is separate, so 
what you are asking for here is that apps-menu and places-menu *both* add top 
bars to non-primary monitors. We are definitely not going to add two or more 
stacked panels at the top.

  What you probably want instead is an option in gnome-shell to put top bars on 
non-primary monitors, and the aforementioned extensions to handle that case.
  "

  "
  Well, we've established what you want, but that doesn't necessarily mean that 
we'll implement it.

  So far the reasoning seems to be:
   - you really want the feature
   - GNOME 2 / Windows has it

  Unlike the case of the window list, nothing in the top bar (except for
  the app menu to some extent) is tied to a particular monitor, so
  there's a much weaker case here IMHO.

  (I'll also note that this wouldn't be a "cheap" option, but require work on 
lots of details throughout the stack - we'd need to figure out the overview 
(only include the activities button on the primary monitor? or allow an 
overview on any monitor?), get API to control the brightness of a particular 
monitor (rather than the built-in one), don't use "the monitor with the top 
bar" as indicator for the primary monitor in Settings, ...)
  "

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


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

[Desktop-packages] [Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently

2022-08-29 Thread Marcos Alano

I achieved level 3 with a fix that will be released for fwupd to
correctly detect the presence of Intel CET feature. That is my original
bug report: https://github.com/fwupd/fwupd/issues/4960

** Bug watch added: github.com/fwupd/fwupd/issues #4960
https://github.com/fwupd/fwupd/issues/4960

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

Title:
43: New Device Security feature is confusing and unhelpful currently

Status in gnome-control-center package in Ubuntu:
Fix Released

Bug description:
GNOME 43 added a new Device Security feature in the Settings app.

You can access it in gnome-control-center 1:43~beta-1ubuntu1
1. Open the Settings app
2. Click Privacy then Device Security

The Security Events aren't clickable.

A default Ubuntu install only gets us "Security Level 1". The highest
level is "Security Level 3".

There isn't anything an Ubuntu user can do to get to a higher security
level from the Device Security screen.

If a user attempts to get their system to a higher security level, I
think they could break their system since this isn't something we
currently support.

Therefore, I think we ought to hide/disable the screen for Ubuntu
22.10. We can work towards better integrating this screen for Ubuntu
in future releases.

I'm attaching several screenshots although it's worth trying out the
feature for yourself too.

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

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

[Desktop-packages] [Bug 1983645] Re: Can't find 5G option in Network Mode under Mobile Network

2022-08-29 Thread Chris Halse Rogers

Hello Dirk, or anyone else affected,

Accepted gnome-control-center into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-control-
center/1:41.7-0ubuntu0.22.04.5 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

Title:
  Can't find 5G option in Network Mode under Mobile Network

Status in OEM Priority Project:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  There is no 5G related option in Network Mode under Mobile Network

  [Test case]
  1. System should have 5G capable hardware (SIM and WWAN module) and 5G 
enabled Modem Manager (>=1.19.1)
  2. Enable mobile network
  3. Check network mode
  4. There should be 5G related option

  [Where problems could occur]
  gnome-control-center interact with Modem Manager to get current network mode 
and set preferred network mode. Modem Manager will filter the unsupported mode. 
The risk will be low.

  [Other info]
  This patch is from upstream gnome-control-center. For more information
  refer to 
https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1388

  The patch also adds some new user visible strings, those will be
  translatable on launchpad and initially displayed in english but we
  can get translations updated then as part of the next language packs
  refresh

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


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

[Desktop-packages] [Bug 1988100] Re: Video thumbnails fail to genetate

** Description changed:

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

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

Title:
  Video thumbnails fail to genetate

Status in totem package in Ubuntu:
  New

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

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

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

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

  Passing the -l flag causes it to work fine.

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

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

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

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

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


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

[Desktop-packages] [Bug 1988100] [NEW] Video thumbnails fail to genetate

Public bug reported:

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

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

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

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

Passing the -l flag causes it to work fine.

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

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

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

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

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


** Tags: amd64 apport-bug jammy

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

Title:
  Video thumbnails fail to genetate

Status in totem package in Ubuntu:
  New

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

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

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

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

  Passing the -l flag causes it to work fine.

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

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

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

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

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


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

[Desktop-packages] [Bug 1987945] Re: [snap] chromium does not read root-owned files in $HOME

Arguably, the case for files not owned by the user in their home
directory is not very widespread.

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

Title:
[snap] chromium does not read root-owned files in $HOME

Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:
Today, I literally spent hours trying to figure out why I cound't
upload a large file.

Of course I thought the problem was the size of the file.

It wasn't. The problem was that Chromium in Snap for some reason is
confined so that it can SEE file-owned-by-root.zip, but NOT READ file-
owned-by-root.zip.

I tried to upload the big file onto a PsiTransfer webpage. And it
simply stalled. The apache2 backend reported 400-errors and I got no
useful info out of that.

Chromium itself reported this in the Networking tab:

PATCH https://PSITRANSFER_HOST/path net::ERR_FAILED

Which is totally useless. In no way could I expect that the ultimate
cause was that the local file was not owned by me.

_If I can see the file, and I have read-permissions on it, I expect
that I can upload the file._

Another example:

$ ls -l ~/Junk/rode_muur*
-rw-rw-r-- 1 walter walter 64773 aug 27 18:08 /home/walter/Junk/rode_muur.jpg
-rw-rw-r-- 1 root root 64773 aug 27 18:08
/home/walter/Junk/rode_muur_root.jpg

Trying to upload rode_muur_root.jpg to e.g.
https://www.filestack.com/fileschool/html/html-file-upload-tutorial-
example/ yields this error-page:

This site can’t be reached
The webpage at
https://www.filestack.com/fileschool/html/html-file-upload-tutorial-example/fileupload.php
might be temporarily down or it may have moved permanently to a new web
address.
ERR_ACCESS_DENIED

That does not tell me that there is a problem with the local file.
That looks like a remote problem, am I right?

What would be the fix?

- Either don't show the file, if you're not letting me access it;
- or let me access the file;
- or, if that isn't possible, give me a reasonable error message. Having to
look in journalctl [1] as root to find out why a client application is
misbehaving is just not acceptable.

[1] # journalctl -t audit -n1 -o cat
AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium"
name="/home/walter/Junk/rode_muur_root.jpg" pid=768825 comm="ThreadPoolForeg"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

(I know that I'll be complaining to deaf ears. You have your reasons
for putting all the browsers in snap. But from a user's perspective,
this whole snap thing has been One Giant Disappointment. I'm actually
considering moving to alternative distros after more than 10 perfectly
satisfactory years on Ubuntu.)

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

[Desktop-packages] [Bug 1987945] Re: [snap] chromium does not read root-owned files, but reports useless errors

That's probably because by default the home interface doesn't allow
access to files not owned by $USER.

The interface has a "read" attribute that, when set to "all", allows
this behaviour. See https://snapcraft.io/docs/home-interface for details
(I wasn't aware of this subtlety of the interface until now). Setting
that attribute makes the interface not autoconnect by default, though.

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

** Tags added: snap

** Summary changed:

- [snap] chromium does not read root-owned files, but reports useless errors
+ [snap] chromium does not read root-owned files in $HOME

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

Title:
[snap] chromium does not read root-owned files in $HOME

Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:
Today, I literally spent hours trying to figure out why I cound't
upload a large file.

Of course I thought the problem was the size of the file.

It wasn't. The problem was that Chromium in Snap for some reason is
confined so that it can SEE file-owned-by-root.zip, but NOT READ file-
owned-by-root.zip.

I tried to upload the big file onto a PsiTransfer webpage. And it
simply stalled. The apache2 backend reported 400-errors and I got no
useful info out of that.

Chromium itself reported this in the Networking tab:

PATCH https://PSITRANSFER_HOST/path net::ERR_FAILED

Which is totally useless. In no way could I expect that the ultimate
cause was that the local file was not owned by me.

_If I can see the file, and I have read-permissions on it, I expect
that I can upload the file._

Another example:

$ ls -l ~/Junk/rode_muur*
-rw-rw-r-- 1 walter walter 64773 aug 27 18:08 /home/walter/Junk/rode_muur.jpg
-rw-rw-r-- 1 root root 64773 aug 27 18:08
/home/walter/Junk/rode_muur_root.jpg

Trying to upload rode_muur_root.jpg to e.g.
https://www.filestack.com/fileschool/html/html-file-upload-tutorial-
example/ yields this error-page:

That does not tell me that there is a problem with the local file.
That looks like a remote problem, am I right?

What would be the fix?

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

[Desktop-packages] [Bug 1960077] Re: Update librest to 1.0 API

This bug was fixed in the package librest - 0.9.1-0ubuntu1

---
librest (0.9.1-0ubuntu1) kinetic; urgency=medium

  * New upstream release required for GNOME 43 (LP: #1960077)
- Update for API bump to 1.0
- Build with meson
- Switch to libsoup3
  * Don't build the examples

 -- Jeremy Bicha   Tue, 23 Aug 2022 19:46:47 -0400

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

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

Title:
  Update librest to 1.0 API

Status in librest package in Ubuntu:
  Fix Released

Bug description:
  This will require sourceful uploads since projects previously built
  against librest-0.7

  I will be running this transition after gnome-shell 43 migrates out of
  kinetic-proposed.

  Some packages will need to be removed LP: #1987432

  I'm working with the Debian maintainer to get this version uploaded to
  Debian Experimental.

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


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

[Desktop-packages] [Bug 1988062] Re: Tests are failing on builders with proxy set

2022-08-29 Thread Jeremy Bicha

** Changed in: glib-networking (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Tests are failing on builders with proxy set

Status in glib-networking package in Ubuntu:
  Fix Committed

Bug description:
  Reported upstream https://gitlab.gnome.org/GNOME/glib-
  networking/-/issues/195

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


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

[Desktop-packages] [Bug 1987945] Re: [snap] chromium does not read root-owned files, but reports useless errors

2022-08-29 Thread Walter

Outside snap:

--

$ cmp Junk/rode_muur.jpg Junk/rode_muur_root.jpg 
(no output, files are equal)

--

Inside Chromium snap confinement:

--

[snap]$ cmp Junk/rode_muur.jpg Junk/rode_muur_root.jpg 
cmp: Junk/rode_muur_root.jpg: Permission denied

--

[snap]$ stat Junk/rode_muur_root.jpg 
  File: Junk/rode_muur_root.jpg
  Size: 64773   Blocks: 128IO Block: 4096   regular file
Device: fd01h/64769dInode: 11017147Links: 1
Access: (0664/-rw-rw-r--)  Uid: (0/root)   Gid: (0/root)
Access: 2022-08-29 21:39:39.249598358 +0200
Modify: 2022-08-27 18:08:23.703069049 +0200
Change: 2022-08-27 18:08:28.839077299 +0200
 Birth: -

--

[snap]$ diff -pu <(stat Junk/rode_muur.jpg) <(stat Junk/rode_muur_root.jpg)
--- /dev/fd/63  2022-08-29 21:42:55.718167721 +0200
+++ /dev/fd/62  2022-08-29 21:42:55.722167732 +0200
@@ -1,8 +1,8 @@
-  File: Junk/rode_muur.jpg
+  File: Junk/rode_muur_root.jpg
   Size: 64773  Blocks: 128IO Block: 4096   regular file
-Device: fd01h/64769d   Inode: 11017139Links: 1
-Access: (0664/-rw-rw-r--)  Uid: ( 1000/  walter)   Gid: ( 1000/  walter)
-Access: 2022-08-29 21:39:47.185621370 +0200
-Modify: 2022-08-27 18:08:17.979060004 +0200
-Change: 2022-08-27 18:08:17.979060004 +0200
+Device: fd01h/64769d   Inode: 11017147Links: 1
+Access: (0664/-rw-rw-r--)  Uid: (0/root)   Gid: (0/root)
+Access: 2022-08-29 21:39:39.249598358 +0200
+Modify: 2022-08-27 18:08:23.703069049 +0200
+Change: 2022-08-27 18:08:28.839077299 +0200
  Birth: -

--

Can't tell from stat that I'm disallowed. In fact, if I have group read
perms, I still cannot read it:

--

[snap]$ id
uid=1000(walter) gid=1000(walter) 
groups=1000(walter),4(adm),20(dialout),24(cdrom),27(sudo),29(audio),30(dip),46(plugdev),113(lpadmin),128(sambashare),139(docker)

--

[snap]$ ls -l Junk/rode_muur*
-rw-rw-r-- 1 walter walter 64773 aug 27 18:08 Junk/rode_muur.jpg
-rw-rw-r-- 1 root   root   64773 aug 27 18:08 Junk/rode_muur_root.jpg
-rw-rw-r-- 1 root   walter 64773 aug 27 18:08 Junk/rode_muur_rootuser.jpg

--

[snap]$ cmp Junk/rode_muur.jpg Junk/rode_muur_rootuser.jpg 
cmp: Junk/rode_muur_rootuser.jpg: Permission denied

--

[snap]$ stat Junk/rode_muur_rootuser.jpg
  File: Junk/rode_muur_rootuser.jpg
  Size: 64773   Blocks: 128IO Block: 4096   regular file
Device: fd01h/64769dInode: 11017142Links: 1
Access: (0664/-rw-rw-r--)  Uid: (0/root)   Gid: ( 1000/  walter)
Access: 2022-08-29 21:39:39.249598358 +0200
Modify: 2022-08-27 18:08:23.703069049 +0200
Change: 2022-08-29 21:47:17.446925673 +0200
 Birth: -

--

FYI, /etc has different confinement, where root files _can_ be read:

--

[snap]$ ls -lda /etc
drwxr-xr-x 179 root root 12288 aug 28 16:49 /etc

--

[snap]$ ls /etc/
ls: cannot open directory '/etc/': Permission denied

--

[snap]$ ls -l /etc/hostname
-rw-r--r-- 1 root root 20 jun 16  2020 /etc/hostname

--

[snap]$ cat /etc/hostname
walter-tretton.kiwi

--

Versions:

--

$ snap version
snap2.56.2+22.04ubuntu1
snapd   2.56.2+22.04ubuntu1
series  16
ubuntu  22.04
kernel  5.15.0-41-generic

--

$ snap list | grep chrom
chromium104.0.5112.79   2051   latest/stable  
canonical**  -

--

$ namei -l /home/walter/Junk/rode_muur_root.jpg 
f: /home/walter/Junk/rode_muur_root.jpg
drwxr-xr-x root   root   /
drwxr-xr-x root   root   home
drwx-- walter walter walter
drwxr-xr-x walter walter Junk
-rw-rw-r-- root   root   rode_muur_root.jpg

--

I don't think I have anything exotic here. My homedir is 0700, but
changing that to 0755 did not change anything.

The files are all on the same / ext4 filesystem (encrypted lvm).

--

Firefox in Snap appears to suffer from the same problem:

--

$ snap run --shell firefox

--

[snap]$ cmp Junk/rode_muur.jpg Junk/rode_muur_root.jpg 
cmp: rode_muur_root.jpg: Permission denied

--

Let me know if I can get you any other info. I have 0 clue how the
confinement rules are configured in snap, so I don't know how to list
that.

Walter

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

Title:
  [snap] chromium does not read root-owned files, but reports useless
  errors

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Today, I literally spent hours trying to figure out why I cound't
  upload a large file.

  Of course I thought the problem was the size of the file.

  It wasn't. The problem was that Chromium in Snap for some reason is
  confined so that it can SEE file-owned-by-root.zip, but NOT READ file-
  owned-by-root.zip.

  I tried to upload the big file onto a PsiTransfer webpage. And it
  simply stalled. The apache2 backend reported 400-errors and I got no
  useful info out of that.

  Chromium itself reported this in the Networking tab:

PATCH https://PSITRANSFER_HOST/path  net::ERR_FAILED

  Which is totally useless. In no way

[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-29 Thread Douglas E Engert

Thanks for the ldd output.
libpcsclite.so.1 is the lib to used the pcscd socket, and is used by modules 
libstpkcs11.so, libeToken.so.10.7.77 and libopensc.so.8 (see below)   It is not 
used in libbit4xpki.so which may be a software pkcs11 or does not use pcscd.  

libcrypto.so.1.1 is OpenSSL-1.1 and also used by modules libstpkcs11.so
and opensc-pkcs11.so

So libstpkcs11.so, libeToken.so.10.7.77 and libstpkcs11.so,
libeToken.so.10.7.77 all appear to work as all the libs are available.

The difference is opensc-pkcs11.so needs to load libopensc.so.8 and a
few others that I have not looked at


On a 22.04.1 system running the command  `sudo snap run --shell 
firefox.firefox` will run snap as root to have snap start up a shell with the 
environment that firefox would run under. 

The `df` command shows:
 
/dev/sda3   122388080  11202960  104921928  10% /var/lib/snapd/hostfs
tmpfs  814036  1272 812764   1% /run
tmpfs5120 4   5116   1% /run/lock
tmpfs  814036   100 813936   1% /run/user/1000
/dev/loop0128   128  0 100% /snap/bare/5
/dev/loop1  63488 63488  0 100% /snap/core20/1587
/dev/loop2  63488 63488  0 100% /
/dev/loop3 167296167296  0 100% /snap/firefox/1635
/dev/loop4 181248181248  0 100% /snap/firefox/1749
/dev/loop5 410496410496  0 100% /snap/gnome-3-38-2004/112
/dev/loop7  48128 48128  0 100% /snap/snapd/16292
/dev/loop6  93952 93952  0 100% /snap/gtk-common-themes/1535
/dev/sda2  524252  5364 51   2% 
/var/lib/snapd/hostfs/boot/efi
Argonne1952871748 479641924 1473229824  25% /media/sf_Argonne
VM-Shared  1952871748 479641924 1473229824  25% /media/sf_VM-Shared
/dev/loop8 354688354688  0 100% /snap/gnome-3-38-2004/115
udev  4034884 04034884   0% /dev
tmpfs 4070180 04070180   0% /dev/shm
tmpfs 4070180 04070180   0% 
/snap/firefox/1749/data-dir/icons
tmpfs 4070180 04070180   0% 
/snap/firefox/1749/data-dir/sounds
tmpfs 4070180 04070180   0% 
/snap/firefox/1749/data-dir/themes
tmpfs 4070180  19964068184   1% /usr/lib/x86_64-linux-gnu
tmpfs 4070180 04070180   0% /usr/share

and /var/lib/snapd/hostfs is the host's filesystem. I was able to copy
libopensc.so.8.0.0 and symlink libopensc.so.8.0.0 to
/usr/lib/x86_64-linux-gnu FF will still not load opensc-pkcs11.so and it
will be gone on a reboot.

snap does set sone environemt variables that could help:
LD_PRELOAD=:/snap/firefox/1749/gnome-platform/$LIB/bindtextdomain.so
LD_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void:/snap/firefox/1749/usr/lib:/snap/firefox/1749/usr/lib/x86_64-linux-gnu:/snap/firefox/1749/gnome-platform/lib/x86_64-linux-gnu:/snap/firefox/1749/gnome-platform/usr/lib/x86_64-linux-gnu:/snap/firefox/1749/gnome-platform/usr/lib:/snap/firefox/1749/gnome-platform/lib:/snap/firefox/1749/gnome-platform/usr/lib/x86_64-linux-gnu/dri:/var/lib/snapd/lib/gl:/snap/firefox/1749/gnome-platform/usr/lib/x86_64-linux-gnu/libunity:/snap/firefox/1749/gnome-platform/usr/lib/x86_64-linux-gnu/pulseaudio


So this is where I am at. Firefox-esr from debiaen works with opensc. Forefox 
from snap does not. It appears the some effort when it to geting p11-kit to 
start, but all p11-kit does is load other pkcs11 modules, that may have been 
installed using normal apt-get. It the initial comments of this bug report 
there were suggestions to copy the single file if a pkcs11 module to a "doc" 
directory, but no attempt was made to copy dependent libraries that the module 
needs. 

These will only work if missing libraries are in the snap base or of
firefox snap packages.

OpenSC also has a notify capability to tell the user when a card was
inserted or removed. This may add additional complications to getting it
to work under snap.

Not much else I can do.

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680

[Desktop-packages] [Bug 1988087] Re: GNOME Settings has two Screen Blank controls and only one of them works.

2022-08-29 Thread Acceptable Name

Upstream bug report
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2025

Upstream commit that fixes this:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/37f5cbe6af5ea71221309669f8b02d5e423956e7

** Description changed:

GNOME Settings has two Screen Blank controls and only one of them works.
+
+ Expected
+
+ Screen Blank controls should preserve the values you set them to.
+
+ Actual
+
+ One of the two Screen blank controls does not preserve the value that
+ you set it to.

Version Info
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Kinetic Kudu (development branch)
Release: 22.10
Codename: kinetic

$ gnome-control-center --version
gnome-control-center 43.beta

$ dpkg -l gnome-control-center | tail -n 1 | awk '{print $3}'
1:43~beta-1ubuntu2

Reproducing

1. Run gnome-control-center power
2. Change "Screen Blank" from the current setting (e.g. 5 minutes) to a
different value.
3. Change to another panel (tab) and change back to Power.
4. Observe that you Screen Blank setting has reverted to the prior value
(e.g. if you set it to "never" it will return to 5 minutes).
5. Change to the Privacy panel, then to the Screen panel.
6. Change the setting for Blank Screen Display to a different value.
7. Change to another panel and then back to Privacy->Screen.
8. Your change to the value of Blank Screen Display will have been retained
(will be the same as you set it a moment ago).
9. Change to the Power panel and the Screen Blank setting that you selected
will be displayed there too.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-control-center 1:43~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 29 15:14:39 2022
InstallationDate: Installed on 2022-08-29 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
ProcEnviron:
- TERM=xterm-256color
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** No longer affects: gnome-control-center (Debian)

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

Title:
GNOME Settings has two Screen Blank controls and only one of them
works.

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

Bug description:
GNOME Settings has two Screen Blank controls and only one of them
works.

Expected

Screen Blank controls should preserve the values you set them to.

Actual

One of the two Screen blank controls does not preserve the value that
you set it to.

Version Info
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Kinetic Kudu (development branch)
Release: 22.10
Codename: kinetic

$ gnome-control-center --version
gnome-control-center 43.beta

$ dpkg -l gnome-control-center | tail -n 1 | awk '{print $3}'
1:43~beta-1ubuntu2

Reproducing

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-control-center 1:43~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 29 15:14:39 2022
InstallationDate: Installed on 2022-08-29 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=

[Desktop-packages] [Bug 1988087] [NEW] GNOME Settings has two Screen Blank controls and only one of them works.

2022-08-29 Thread Acceptable Name

Public bug reported:

GNOME Settings has two Screen Blank controls and only one of them works.

Expected

Screen Blank controls should preserve the values you set them to.

Actual

One of the two Screen blank controls does not preserve the value that
you set it to.

Version Info
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Kinetic Kudu (development branch)
Release:22.10
Codename:   kinetic

$ gnome-control-center --version
gnome-control-center 43.beta

$ dpkg -l gnome-control-center | tail -n 1 | awk '{print $3}'
1:43~beta-1ubuntu2

Reproducing

1. Run gnome-control-center power
2. Change "Screen Blank" from the current setting (e.g. 5 minutes) to a 
different value.
3. Change to another panel (tab) and change back to Power.
4. Observe that you Screen Blank setting has reverted to the prior value (e.g. 
if you set it to "never" it will return to 5 minutes).
5. Change to the Privacy panel, then to the Screen panel.
6. Change the setting for Blank Screen Display to a different value.
7. Change to another panel and then back to Privacy->Screen.
8. Your change to the value of Blank Screen Display will have been retained 
(will be the same as you set it a moment ago).
9. Change to the Power panel and the Screen Blank setting that you selected 
will be displayed there too.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-control-center 1:43~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 29 15:14:39 2022
InstallationDate: Installed on 2022-08-29 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2025
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2025

** Also affects: gnome-control-center (Debian) via
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2025
   Importance: Unknown
   Status: Unknown

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

Title:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

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

Bug description:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

  Expected

  Screen Blank controls should preserve the values you set them to.

  Actual

  One of the two Screen blank controls does not preserve the value that
  you set it to.

  Version Info
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ gnome-control-center --version
  gnome-control-center 43.beta

  $ dpkg -l gnome-control-center | tail -n 1 | awk '{print $3}'
  1:43~beta-1ubuntu2

  Reproducing

  1. Run gnome-control-center power
  2. Change "Screen Blank" from the current setting (e.g. 5 minutes) to a 
different value.
  3. Change to another panel (tab) and change back to Power.
  4. Observe that you Screen Blank setting has reverted to the prior value 
(e.g. if you set it to "never" it will return to 5 minutes).
  5. Change to the Privacy panel, then to the Screen panel.
  6. Change the setting for Blank Screen Display to a different value.
  7. Change to another panel and then back to Privacy->Screen.
  8. Your change to the value of Blank Screen Display will have been retained 
(will be the same as you set it a moment ago).
  9. Change to the Power panel and the Screen Blank setting that you selected 
will be displayed there too.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 29 15:14:39 2022
  InstallationDate: Installed on 2022-08-29 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePac

[Desktop-packages] [Bug 1987976] Re: firefox black window

2022-08-29 Thread Michelet

Oh I found that https://doc.ubuntu-fr.org/carte_graphique. Result is:
nicolas@nicolas-fixe:~$ lspci -vnn | grep -A 12 '\[030[02]\]' | grep -Ei 
"vga|3d|display|kernel"
01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller])
Kernel driver in use: radeon
Kernel modules: radeon
nicolas@nicolas-fixe:~$ sudo lshw -enable pci -class display
[sudo] Mot de passe de nicolas : 
  *-display 
   description: VGA compatible controller
   produit: RS880 [Radeon HD 4200]
   fabricant: Advanced Micro Devices, Inc. [AMD/ATI]
   identifiant matériel: 5
   information bus: pci@:01:05.0
   nom logique: /dev/fb0
   version: 00
   bits: 32 bits
   horloge: 33MHz
   fonctionnalités: pm msi vga_controller bus_master cap_list rom fb
   configuration : depth=32 driver=radeon latency=0 resolution=1920,1080
   ressources : irq:18 mémoire:d000-dfff portE/S:d000(taille=256) 
mémoire:fe9f-fe9f mémoire:fe80-fe8f mémoire:c-d
nicolas@nicolas-fixe:~$ xrandr
Screen 0: minimum 16 x 16, current 1920 x 1080, maximum 32767 x 32767
XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 
480mm x 270mm
   1920x1080 59.96*+
   1440x1080 59.99  
   1400x1050 59.98  
   1280x1024 59.89  
   1280x960  59.94  
   1152x864  59.96  
   1024x768  59.92  
   800x600   59.86  
   640x480   59.38  
   320x240   59.52  
   1680x1050 59.95  
   1440x900  59.89  
   1280x800  59.81  
   720x480   59.71  
   640x400   59.95  
   320x200   58.96  
   1600x900  59.95  
   1368x768  59.88  
   1280x720  59.86  
   1024x576  59.90  
   864x486   59.92  
   720x400   59.55  
   640x350   59.77

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

Title:
  firefox black window

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1987976] Re: firefox black window

No, I still can't see the attachment. I wonder whether this is a
Launchpad bug?

In any case, it's good to know that the command line I suggested seems to work 
around the problem.
Just to confirm, if you run it with:

MOZ_ENABLE_WAYLAND=0 snap run firefox

you get the black screen again?

For GPU info, you could attach the output of `sudo lshw -C display`.

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

Title:
  firefox black window

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1987985] Re: Totem black screen playing a video

2022-08-29 Thread corrado venturini

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Totem black screen playing a video

Status in gstreamer1.0 package in Ubuntu:
  Invalid

Bug description:
  Click on a video file. totem opens with a black screen.
  problem with webm, avi, mov
  totem: Installed: 43~beta-1ubuntu1
  I open the bug against totem but the bug seems open against gstreamer1.0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libgstreamer1.0-0 1.20.3-1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 17:57:01 2022
  InstallationDate: Installed on 2022-08-11 (16 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220811)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1987985/+subscriptions


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

[Desktop-packages] [Bug 1987976] Re: firefox black window

2022-08-29 Thread Michelet

I've just tried the command line and it worked (no more black screen).

Though the result is :
nicolas@nicolas-fixe:~$ MOZ_ENABLE_WAYLAND=1 snap run firefox
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot open directory "/var/lib": permission denied
Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs

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

Title:
  firefox black window

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1987976] Re: firefox black window

2022-08-29 Thread Michelet

Here is the attachment again. Can you see it now?
I am going to try the command line and tell you thereafter.

Sorry but can you tell me how and where I can gather information about
GPU and drivers?

** Attachment added: "Capture d’écran du 2022-08-27 09-04-23.png"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987976/+attachment/5612428/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202022-08-27%2009-04-23.png

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

Title:
  firefox black window

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-29 Thread Jefferson Ascaneo

It seems there is another smartcard model used by the Italian
government. I though this could be useful as another example:

$ ldd libstpkcs11.so
linux-vdso.so.1 (0x7ffe51f67000)
libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1 
(0x7f394c92a000)
libpcsclite.so.1 => /lib/x86_64-linux-gnu/libpcsclite.so.1 
(0x7f394cfd7000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f394c6fe000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f394c4d6000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f394cfb7000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f394cfb)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f394cfab000)
/lib64/ld-linux-x86-64.so.2 (0x7f394cffe000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f394cec4000)

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-29 Thread Jefferson Ascaneo

I did a quick search and found two deb packages at a Italian government
website containing libbit4xpki.so

This is the output from i386 and amd64 versions:

$ ldd libbit4xpki.so 
linux-gate.so.1 (0xf7f7f000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf7d87000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7d82000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7d7d000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7b48000)
/lib/ld-linux.so.2 (0xf7f81000)

$ ldd libbit4xpki.so 
linux-vdso.so.1 (0x7fff13983000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f329bf5c000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f329bf57000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f329bf52000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f329b9d8000)
/lib64/ld-linux-x86-64.so.2 (0x7f329c05e000)

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1987985] Re: Totem black screen playing a video

2022-08-29 Thread corrado venturini

Wait, it seems nautilus has problems passing arguments to the called 
application: if i start totem by double click on the video and ask totem for 
'Properties' i see a window wit all info 'Unknown' or 'N/A' so let wait for new 
nautilus who is blocked for dependencies
corrado@corrado-n6-kk-0811:~$ apt policy nautilus
nautilus:
  Installed: 1:43~beta.1-2ubuntu2
  Candidate: 1:43~beta.1-2ubuntu3
 ...
The following packages have been kept back:
  burner-common libburner-media3-1 libnautilus-extension4 nautilus

... I found another app having the same problem...

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

Title:
  Totem black screen playing a video

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Click on a video file. totem opens with a black screen.
  problem with webm, avi, mov
  totem: Installed: 43~beta-1ubuntu1
  I open the bug against totem but the bug seems open against gstreamer1.0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libgstreamer1.0-0 1.20.3-1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 17:57:01 2022
  InstallationDate: Installed on 2022-08-11 (16 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220811)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1987985/+subscriptions


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

[Desktop-packages] [Bug 1988071] Re: Update to Unity Control Center to 7.6 version

2022-08-29 Thread Rudra Saraswat

Here's the patch for 7.6 version (between
15.04.0+21.10.20220802-0ubuntu1 and 15.04.0+22.04.20220829-0ubuntu1).
Subscribing Ubuntu sponsors too.

** Patch added: "unity-control-center_15.04.0+22.04.20220829-0ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1988071/+attachment/5612390/+files/unity-control-center_15.04.0+22.04.20220829-0ubuntu1.debdiff

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

Title:
  Update to Unity Control Center to 7.6 version

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

Bug description:
  This version of Unity Control Center fixes many bugs, like the broken
  theme selector.

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


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

[Desktop-packages] [Bug 1988071] [NEW] Update to Unity Control Center to 7.6 version

2022-08-29 Thread Rudra Saraswat

Public bug reported:

This version of Unity Control Center fixes many bugs, like the broken
theme selector.

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Update to Unity Control Center to 7.6 version

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

Bug description:
  This version of Unity Control Center fixes many bugs, like the broken
  theme selector.

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


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

[Desktop-packages] [Bug 1987979] Re: Firefox Narrator stopped working after upgrade from 20.04 to 22.04

This is a known issue, which is being tracked in the upstream bug
tracker: https://bugzilla.mozilla.org/show_bug.cgi?id=1729750

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

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1729750
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Firefox Narrator stopped working after upgrade from 20.04 to 22.04
+ [snap] Firefox Narrator stopped working after upgrade from 20.04 to 22.04

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

Title:
  [snap] Firefox Narrator stopped working after upgrade from 20.04 to
  22.04

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  New

Bug description:
  I just noticed that the narrator feature, which reads articles out
  load with TTS in Firefox reading view stopped working after upgrading
  to 22.04. Another user reported the same problem on ask Ubuntu:

  https://askubuntu.com/questions/1418391/no-tts-voices-on-
  firefox-v102-0-after-upgrading-to-ubuntu-22-04-lts

  Also, if you have no clue what this is about:
  https://askubuntu.com/questions/953509/how-can-i-change-the-voice-
  used-by-firefox-reader-view-narrator-in-ubuntu

  ---

  1)

  $   lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  2) Firefox is a snap now, but I guess for the feature to work it needs
  to detect TTS which is packaged as deb.

  $  snap list firefox
  Name Version  Rev   Tracking   Publisher  Notes
  firefox  104.0-3  1749  latest/stable  mozilla✓   -

  $  apt-cache policy espeak speech-dispatcher-espeak-ng firefox
  espeak:
    Installed: 1.48.15+dfsg-3
    Candidate: 1.48.15+dfsg-3
    Version table:
   *** 1.48.15+dfsg-3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status
  speech-dispatcher-espeak-ng:
    Installed: 0.11.1-1ubuntu1
    Candidate: 0.11.1-1ubuntu1
    Version table:
   *** 0.11.1-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.11.1-1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  firefox:
    Installed: (none)
    Candidate: 1:1snap1-0ubuntu2
    Version table:
   1:1snap1-0ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  3) open a website, enter reader mode, click the icon with sound waves
  and hear the text being read with TTS

  4) the icon is missing

  ---

  Edit: I tested Firefox Flatpak and it is also affected, my best guess
  is that Firefox is not at fault.

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


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

[Desktop-packages] [Bug 1987976] Re: firefox black window

It appears that I cannot see the attached screenshot. Can you maybe try
re-attaching it?

Can you share some details about your hardware (particularly GPU and
drivers in use)?

Does it make any difference if you run it like this?

MOZ_ENABLE_WAYLAND=1 snap run firefox

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

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

Title:
  firefox black window

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1988033] Re: Login screen is missing the Ubuntu logo

This bug was fixed in the package plymouth - 22.02.122-1ubuntu3

---
plymouth (22.02.122-1ubuntu3) kinetic; urgency=medium

  * debian/rules:
- restore /usr/share/plymouth/ubuntu-logo.png, it's used by other
  components like gnome-shell (lp: #1988033)

 -- Sebastien Bacher   Mon, 29 Aug 2022 12:03:49
+0200

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

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

Title:
  Login screen is missing the Ubuntu logo

Status in plymouth package in Ubuntu:
  Fix Released

Bug description:
  Login screen is missing the Ubuntu logo since the latest updates to
  kinetic.

  Looks like plymouth 22.02.122-1ubuntu2 might have triggered it.

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


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

[Desktop-packages] [Bug 1987945] Re: [snap] chromium does not read root-owned files, but reports useless errors

Thanks for the report Walter. This hasn't fallen on deaf ears. Reading
and uploading a file to which you have read permissions in your home
directory is definitely something that's expected to work, and if it
doesn't it needs to be investigated and fixed.

Can you try the following?

snap run --shell chromium
stat $SNAP_REAL_HOME/Junk/rode_muur_root.jpg
exit

and share the output here?

Is there anything "exotic" (i.e. non-default options) about your home
directory?

** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete

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

Title:
[snap] chromium does not read root-owned files, but reports useless
errors

Status in chromium-browser package in Ubuntu:
Incomplete

Bug description:
Today, I literally spent hours trying to figure out why I cound't
upload a large file.

Of course I thought the problem was the size of the file.

It wasn't. The problem was that Chromium in Snap for some reason is
confined so that it can SEE file-owned-by-root.zip, but NOT READ file-
owned-by-root.zip.

I tried to upload the big file onto a PsiTransfer webpage. And it
simply stalled. The apache2 backend reported 400-errors and I got no
useful info out of that.

Chromium itself reported this in the Networking tab:

PATCH https://PSITRANSFER_HOST/path net::ERR_FAILED

Which is totally useless. In no way could I expect that the ultimate
cause was that the local file was not owned by me.

_If I can see the file, and I have read-permissions on it, I expect
that I can upload the file._

Another example:

$ ls -l ~/Junk/rode_muur*
-rw-rw-r-- 1 walter walter 64773 aug 27 18:08 /home/walter/Junk/rode_muur.jpg
-rw-rw-r-- 1 root root 64773 aug 27 18:08
/home/walter/Junk/rode_muur_root.jpg

Trying to upload rode_muur_root.jpg to e.g.
https://www.filestack.com/fileschool/html/html-file-upload-tutorial-
example/ yields this error-page:

That does not tell me that there is a problem with the local file.
That looks like a remote problem, am I right?

What would be the fix?

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

[Desktop-packages] [Bug 1987933] Re: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

Relevant debug info from DpkgTerminalLog.txt:

Preparing to unpack .../15-firefox_1%3a1snap1-0ubuntu2_amd64.deb ...
=> Installing the firefox snap
==> Checking connectivity with the snap store
dpkg: error processing archive 
/tmp/apt-dpkg-install-Sum4bs/15-firefox_1%3a1snap1-0ubuntu2_amd64.deb 
(--unpack):
 new firefox package pre-installation script subprocess returned error exit 
status 1


Were you online when you upgraded to 22.04 ? Installing the firefox update 
requires a connection to the snap store.

You can try updating it again (ensure you're connected to the internet):

sudo apt reinstall firefox


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

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

Title:
  package firefox 104.0+build3-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  NOT SURE

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  home   1370 F pulseaudio
   /dev/snd/controlC1:  home   1370 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Fri Aug 26 15:16:30 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-08-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IpRoute:
   default via 192.168.43.1 dev wlx20e41702fe19 proto dhcp metric 600 
   169.254.0.0/16 dev wlx20e41702fe19 scope link metric 1000 
   192.168.43.0/24 dev wlx20e41702fe19 proto kernel scope link src 
192.168.43.250 metric 600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-08-26 (0 days ago)
  dmi.bios.date: 07/26/2021
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/26/2021:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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


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

[Desktop-packages] [Bug 1838008] Re: [snap] cursor theme isn't respected

So you're unpacking gtk-common-themes, adding something (xxx ?) to the
icon theme, and repacking it. Can you explain why you're doing that?

The correct way would be to submit a PR against
https://github.com/ubuntu/gtk-common-themes, which would address the
problem you're encountering for everyone, and would ensure your
modifications aren't discarded the next time the snap is updated.

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

Title:
  [snap] cursor theme isn't respected

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in xubuntu-default-settings package in Ubuntu:
  Fix Released

Bug description:
  (initially reported at https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/85)

  When changing the cursor theme with gnome-tweaks, I can observe that
  some themes aren't respected in the chromium snap. This appears to be
  specific to chromium, other snaps like evince or gimp use the correct
  cursors.

  Yaru and Adwaita are fine, but Redglass or Whiteglass aren't.

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


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

[Desktop-packages] [Bug 1988062] [NEW] Tests are failing on builders with proxy set

Public bug reported:

Reported upstream https://gitlab.gnome.org/GNOME/glib-
networking/-/issues/195

** Affects: glib-networking (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: update-excuse

** Changed in: glib-networking (Ubuntu)
   Importance: Undecided => High

** Changed in: glib-networking (Ubuntu)
   Status: New => Triaged

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

Title:
  Tests are failing on builders with proxy set

Status in glib-networking package in Ubuntu:
  Triaged

Bug description:
  Reported upstream https://gitlab.gnome.org/GNOME/glib-
  networking/-/issues/195

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


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

[Desktop-packages] [Bug 1988063] [NEW] import openvpn config based on pkcs12 cert fail

2022-08-29 Thread Winfried Muench

Public bug reported:

With Ubuntu 20.04 i can import a openvpn.conf with pkcs12 cert in Ubuntu
22.04 i got the errormessage:


sudo nmcli connection import type openvpn file abk.ovpn 
Fehler: Importieren von abk.ovpn ist fehlgeschlagen: Die zu importierende Datei 
war keine gültige OpenVPN Konfiguration (--ca darf nicht das PKCS#12 Format 
haben).

I found this bugfix on GNOME/Network-manager-openvpn
https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/merge_requests/50

Please Fix this also in Ubuntu.

Regards
Wim

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  import openvpn config based on pkcs12 cert fail

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  With Ubuntu 20.04 i can import a openvpn.conf with pkcs12 cert in
  Ubuntu 22.04 i got the errormessage:

  
  sudo nmcli connection import type openvpn file abk.ovpn 
  Fehler: Importieren von abk.ovpn ist fehlgeschlagen: Die zu importierende 
Datei war keine gültige OpenVPN Konfiguration (--ca darf nicht das PKCS#12 
Format haben).

  I found this bugfix on GNOME/Network-manager-openvpn
  https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/merge_requests/50

  Please Fix this also in Ubuntu.

  Regards
  Wim

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


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

[Desktop-packages] [Bug 1987985] Re: Totem black screen playing a video

2022-08-29 Thread corrado venturini

I have some video files in my Videos directory. Playing them from command line 
gives no problem and the video is correctly played also with sound 
corrado@corrado-n6-kk-0811:~$ cd Videos
corrado@corrado-n6-kk-0811:~/Videos$ ls
Screencasts  x.AVI  x.MOV  x.mp4  x.webm
corrado@corrado-n6-kk-0811:~/Videos$ totem x.webm 
corrado@corrado-n6-kk-0811:~/Videos$ totem x.AVI 
corrado@corrado-n6-kk-0811:~/Videos$ totem x.mp4 
corrado@corrado-n6-kk-0811:~/Videos$ totem x.MOV 
corrado@corrado-n6-kk-0811:~/Videos$ 
but if do double click on any of the files i have a black screen.
same with right click on file and selecting 'open with videos'

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

Title:
  Totem black screen playing a video

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Click on a video file. totem opens with a black screen.
  problem with webm, avi, mov
  totem: Installed: 43~beta-1ubuntu1
  I open the bug against totem but the bug seems open against gstreamer1.0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libgstreamer1.0-0 1.20.3-1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 17:57:01 2022
  InstallationDate: Installed on 2022-08-11 (16 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220811)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1987985/+subscriptions


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

[Desktop-packages] [Bug 1981937] Re: Update gnome-shell to 42.3.1

This bug was fixed in the package gnome-shell - 42.4-0ubuntu0.22.04.1

---
gnome-shell (42.4-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #1985304):
- Fix logging in with realmd (LP: #1985128)
  * debian/patches: Refresh and drop applied upstream

 -- Marco Trevisan (Treviño)   Thu, 11 Aug 2022
17:58:27 -0400

** Changed in: gnome-shell (Ubuntu Jammy)
   Status: In Progress => 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/1981937

Title:
  Update gnome-shell to 42.3.1

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

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series (42.3 and 42.3.1)

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

  It is hoped that this update will be included in Ubuntu 22.04.1

  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/1981937/+subscriptions


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

[Desktop-packages] [Bug 1981952] Re: gnome-shell-extension-manager update feature doesn't work unless gnome-shell-extension-prefs is installed

This bug was fixed in the package gnome-shell - 42.4-0ubuntu0.22.04.1

---
gnome-shell (42.4-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #1985304):
- Fix logging in with realmd (LP: #1985128)
  * debian/patches: Refresh and drop applied upstream

 -- Marco Trevisan (Treviño)   Thu, 11 Aug 2022
17:58:27 -0400

** Changed in: gnome-shell (Ubuntu Jammy)
   Status: In Progress => 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/1981952

Title:
  gnome-shell-extension-manager update feature doesn't work unless
  gnome-shell-extension-prefs is installed

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

Bug description:
  Impact
  --
  There are 2 apps available in Ubuntu 22.04 LTS to manage extensions: the 
older Extensions app built as part of GNOME Shell but included in a separate 
binary package (gnome-shell-extension-prefs) and the newer third party 
Extension Manager from Matt Jakeman (packaged as gnome-shell-extension-manager).

  Extension Manager has a feature that automatically updates GNOME Shell
  extensions (like the Extensions app). However, the feature wasn't
  working unless the Extensions app was also installed because GNOME
  Shell didn't recognize the Extension Manager app as permitted to
  update GNOME Shell extensions.

  Test Case
  -
  0. Make sure you don't have the gnome-shell-extension-prefs app installed. 
Open a terminal and run
  sudo apt remove gnome-shell-extension-prefs
  1. Extract the bluetooth-quick-connect-27 archive to 
~/.local/share/gnome-shell/extensions/
  This should create a folder:
  
~/.local/share/gnome-shell/extensions/bluetooth-quick-conn...@bjarosze.gmail.com
  2. Install the updated gnome-shell packages
  3. Open a terminal and run
  sudo apt install gnome-shell-extension-manager gnome-shell-extension-manager
  4. Log out
  5. Log in
  6. You should see a notification letting you know that there is an extension 
update available.
  7. Click the notification. The Extension Manager app will open.
  8. At the bottom of the app is a message like:
  "Updates are available. One extension will be updated on next login."
  Click  the Log Out button.
  9. Log in.
  10. Open the Extension Manager app. Click the Bluetooth Quick Connect row. It 
should show the version number as greater than 27 (in my testing, the new 
version was 29 but new versions can be released at any time). You can also 
click the button to remove the extension if you want. Or you can turn the 
extension on if you want.

  What Could Go Wrong
  ---
  This is a minimal patch cherry-picked from the gnome-shell master branch.

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


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

[Desktop-packages] [Bug 1985128] Re: GDM fails to activate the login session in AWS Workspaces

This bug was fixed in the package gnome-shell - 42.4-0ubuntu0.22.04.1

---
gnome-shell (42.4-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #1985304):
- Fix logging in with realmd (LP: #1985128)
  * debian/patches: Refresh and drop applied upstream

 -- Marco Trevisan (Treviño)   Thu, 11 Aug 2022
17:58:27 -0400

** Changed in: gnome-shell (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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1985128

Title:
  GDM fails to activate the login session in AWS Workspaces

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

Bug description:
  [Impact]

  This is the main error:

  Aug 05 18:05:39 ip-198-19-76-222 gdm3[837]: Gdm: GdmSession: conversation 
dcv-graphical-sso started more than once
  Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: _reportInitError 
dcv-graphical-sso
  Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: JS ERROR: Failed to start 
dcv-graphical-sso verification: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.Failed: Could not create 
authentication >
  
_promisify/proto[asyncFunc]/https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1985128/+subscriptions


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

[Desktop-packages] [Bug 1985128] Update Released

2022-08-29 Thread Łukasz Zemczak

The verification of the Stable Release Update for gnome-shell 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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1985128

Title:
  GDM fails to activate the login session in AWS Workspaces

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

Bug description:
  [Impact]

  This is the main error:

  Aug 05 18:05:39 ip-198-19-76-222 gdm3[837]: Gdm: GdmSession: conversation 
dcv-graphical-sso started more than once
  Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: _reportInitError 
dcv-graphical-sso
  Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: JS ERROR: Failed to start 
dcv-graphical-sso verification: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.Failed: Could not create 
authentication >
  
_promisify/proto[asyncFunc]/https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1985128/+subscriptions


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

[Desktop-packages] [Bug 1985304] Update Released

2022-08-29 Thread Łukasz Zemczak

The verification of the Stable Release Update for gnome-shell 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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1985304

Title:
  Update GNOME Shell to 42.4

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

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

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

  The version currently in Ubuntu 22.04.1 LTS is 42.2

  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.
  Verify that the basic functionality of each extension works as expected.

  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/1985304/+subscriptions


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

[Desktop-packages] [Bug 1985304] Re: Update GNOME Shell to 42.4

This bug was fixed in the package gnome-shell - 42.4-0ubuntu0.22.04.1

---
gnome-shell (42.4-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #1985304):
- Fix logging in with realmd (LP: #1985128)
  * debian/patches: Refresh and drop applied upstream

 -- Marco Trevisan (Treviño)   Thu, 11 Aug 2022
17:58:27 -0400

** Changed in: gnome-shell (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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1985304

Title:
  Update GNOME Shell to 42.4

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

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

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

  The version currently in Ubuntu 22.04.1 LTS is 42.2

  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.
  Verify that the basic functionality of each extension works as expected.

  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/1985304/+subscriptions


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

[Desktop-packages] [Bug 1988052] [NEW] Nautilus can't extract RAR files with password protected

2022-08-29 Thread Ayron Grenier

Public bug reported:

I recently install Ubuntu 22.04.1 and I installed unrar package. But if
I open a password protected .rar file in Nautilus with Extract here...
it should ask for the password, but instead it shows the error "There
was an error extracting name.rar RAR encryption support unavailable."

Via a terminal with unrar e name.rar it works as expected and if I double click 
on the RAR file, it opens a window and asks for the password and work nicely 
extracting the content.
 
In Ubuntu 20.04 this works fine.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 29 09:25:37 2022
InstallationDate: Installed on 2022-08-03 (25 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 evince42.3-0ubuntu2
 file-roller   3.42.0-1
 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
 nautilus-share0.7.3-2ubuntu6

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


** Tags: file-roller jammy nautilus unrar

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

Title:
  Nautilus can't extract RAR files with password protected

Status in nautilus package in Ubuntu:
  New

Bug description:
  I recently install Ubuntu 22.04.1 and I installed unrar package. But
  if I open a password protected .rar file in Nautilus with Extract
  here... it should ask for the password, but instead it shows the error
  "There was an error extracting name.rar RAR encryption support
  unavailable."

  Via a terminal with unrar e name.rar it works as expected and if I double 
click on the RAR file, it opens a window and asks for the password and work 
nicely extracting the content.
   
  In Ubuntu 20.04 this works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 29 09:25:37 2022
  InstallationDate: Installed on 2022-08-03 (25 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.3-0ubuntu2
   file-roller   3.42.0-1
   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/1988052/+subscriptions


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

[Desktop-packages] [Bug 1980170] Re: Tapping on the current app's icon in the dock (via touchscreen) doesn't show the current windows (while clicking it does)

2022-08-29 Thread Connor Nolan

Any update on this?

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

Title:
  Tapping on the current app's icon in the dock (via touchscreen)
  doesn't show the current windows (while clicking it does)

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

Bug description:
  # Expected Behavior

  Tapping on an app's icon in the dock behaves just like clicking it. As
  in, clicking the current app shows the open windows in a context menu,
  and clicking any other app's icon, makes the app current.

  # Actual Behavior

  CLicking an app's icon just makes it current, and clicking the current
  app's icon does nothing (unless it's a long-press, then it does what
  you expect.)

  # The Screenshot
  I attached a screenshot of the context menu that comes up when clicking the 
current app's dock icon. This menu doesn't come up when tapping.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.17.0-1006.6-oem 5.17.3
  Uname: Linux 5.17.0-1006-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 28 23:26:59 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-06-14 (380 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-05-10 (49 days ago)

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


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

[Desktop-packages] [Bug 1978411] Re: simple-scan throws error and crashes upon scanning document

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

** Changed in: simple-scan (Ubuntu)
   Status: New => Confirmed

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

Title:
  simple-scan throws error and crashes upon scanning document

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  [+0.00s] DEBUG: simple-scan.vala:1720: Starting simple-scan 3.36.3, PID=94430
  [+0.00s] DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
  [+0.02s] DEBUG: _g_io_module_get_default: Found default implementation dconf 
(DConfSettingsBackend) for ‘gsettings-backend’
  [+0.06s] DEBUG: app-window.vala:1906: Loading state from 
/home/mcapp/.cache/simple-scan/state
  [+0.06s] DEBUG: app-window.vala:1885: Restoring window to 600x400 pixels
  [+0.38s] DEBUG: scanner.vala:1539: sane_init () -> SANE_STATUS_GOOD
  [+0.38s] DEBUG: scanner.vala:1545: SANE version 1.0.29
  [+0.38s] DEBUG: scanner.vala:1606: Requesting redetection of scan devices
  [+0.38s] DEBUG: scanner.vala:828: Processing request
  [+0.57s] DEBUG: app-window.vala:1981: Saving state to 
/home/mcapp/.cache/simple-scan/state
  [+9.67s] DEBUG: app-window.vala:1981: Saving state to 
/home/mcapp/.cache/simple-scan/state
  [+11.26s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
  [+11.26s] DEBUG: scanner.vala:353: Device: name="brother4:net1;dev0" 
vendor="Brother" model="MFC-9130CW" type="MFC-9130CW"
  [+11.55s] DEBUG: app-window.vala:1981: Saving state to 
/home/mcapp/.cache/simple-scan/state
  [+11.70s] DEBUG: app-window.vala:1981: Saving state to 
/home/mcapp/.cache/simple-scan/state
  [+12.68s] DEBUG: simple-scan.vala:1536: Requesting scan at 1200 dpi from 
device 'brother4:net1;dev0'
  [+12.68s] DEBUG: scanner.vala:1674: Scanner.scan ("brother4:net1;dev0", 
dpi=1200, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0, 
paper_height=0, brightness=0, contrast=0, delay=3000ms)
  [+12.68s] DEBUG: scanner.vala:828: Processing request
  [+12.93s] DEBUG: app-window.vala:1981: Saving state to 
/home/mcapp/.cache/simple-scan/state
  [+14.30s] DEBUG: app-window.vala:1981: Saving state to 
/home/mcapp/.cache/simple-scan/state
  [+18.55s] DEBUG: scanner.vala:889: sane_open ("brother4:net1;dev0") -> 
SANE_STATUS_GOOD
  [+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (0)
  [+18.55s] DEBUG: scanner.vala:760: Option 0: name='(null)' title='Number of 
options' type=bool size=4 cap=soft-detect
  [+18.55s] DEBUG: scanner.vala:763:   Description: Read-only option that 
specifies how many options a specific devices supports.
  [+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (1)
  [+18.55s] DEBUG: scanner.vala:760: Option 1: name='(null)' title='Mode' 
type=group size=4 cap=advanced
  [+18.55s] DEBUG: scanner.vala:763:   Description: 
  [+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (2)
  [+18.55s] DEBUG: scanner.vala:760: Option 2: name='mode' title='Scan mode' 
type=string size=30 values=["Black & White", "Gray[Error Diffusion]", "True 
Gray", "24bit Color", "24bit Color[Fast]"] cap=soft-select,soft-detect
  [+18.55s] DEBUG: scanner.vala:763:   Description: Select the scan mode
  [+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (3)
  [+18.55s] DEBUG: scanner.vala:760: Option 3: name='resolution' title='Scan 
resolution' type=int size=4 unit=dpi values=[100, 150, 200, 300, 400, 600, 
1200, 2400, 4800, 9600] cap=soft-select,soft-detect
  [+18.55s] DEBUG: scanner.vala:763:   Description: Sets the resolution of the 
scanned image.
  [+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (4)
  [+18.55s] DEBUG: scanner.vala:760: Option 4: name='source' title='Scan 
source' type=string size=64 values=["FlatBed", "Automatic Document Feeder(left 
aligned)", "Automatic Document Feeder(centrally aligned)"] 
cap=soft-select,soft-detect
  [+18.55s] DEBUG: scanner.vala:763:   Description: Selects the scan source 
(such as a document-feeder).
  [+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (5)
  [+18.55s] DEBUG: scanner.vala:760: Option 5: name='brightness' 
title='Brightness' type=fixed size=4 unit=percent min=-50.00, 
max=50.00, quant=65536 cap=soft-select,soft-detect,inactive
  [+18.55s] DEBUG: scanner.vala:763:   Description: Controls the brightness of 
the acquired image.
  [+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (6)
  [+18.55s] DEBUG: scanner.vala:760: Option 6: name='contrast' title='Contrast' 
type=fixed size=4 unit=percent min=-50.00, max=50.00, quant=65536 
cap=soft-select,soft-detect,inactive
  [+18.55s] DEBUG: scanner.vala:763:   Description: Controls the contrast of 
the acquired image.
  [+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (7)
  [+18.55s] DEBUG: scanner.vala:760: Option 7: name='(null)' title='Geometry' 
type=group

[Desktop-packages] [Bug 1988033] Re: Login screen is missing the Ubuntu logo

** No longer affects: ubuntu-settings (Ubuntu)

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

Title:
  Login screen is missing the Ubuntu logo

Status in plymouth package in Ubuntu:
  Fix Committed

Bug description:
  Login screen is missing the Ubuntu logo since the latest updates to
  kinetic.

  Looks like plymouth 22.02.122-1ubuntu2 might have triggered it.

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


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

[Desktop-packages] [Bug 1988033] Re: Login screen is missing the Ubuntu logo

https://launchpad.net/ubuntu/+source/plymouth/22.02.122-1ubuntu3

** Package changed: gnome-shell (Ubuntu) => plymouth (Ubuntu)

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

** Changed in: plymouth (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Login screen is missing the Ubuntu logo

Status in plymouth package in Ubuntu:
  Fix Committed

Bug description:
  Login screen is missing the Ubuntu logo since the latest updates to
  kinetic.

  Looks like plymouth 22.02.122-1ubuntu2 might have triggered it.

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


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

[Desktop-packages] [Bug 1988033] Re: Login screen is missing the Ubuntu logo

Our settings are pointing to a non-existent file now:

org.gnome.login-screen logo '/usr/share/plymouth/ubuntu-logo.png'

which is the responsibility of source package 'ubuntu-settings'.

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

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

Title:
  Login screen is missing the Ubuntu logo

Status in plymouth package in Ubuntu:
  Fix Committed

Bug description:
  Login screen is missing the Ubuntu logo since the latest updates to
  kinetic.

  Looks like plymouth 22.02.122-1ubuntu2 might have triggered it.

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


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

[Desktop-packages] [Bug 1988033] [NEW] Login screen is missing the Ubuntu logo

Public bug reported:

Login screen is missing the Ubuntu logo since the latest updates to
kinetic.

Looks like plymouth 22.02.122-1ubuntu2 might have triggered it.

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


** Tags: kinetic

** Tags added: kinetic

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

Title:
  Login screen is missing the Ubuntu logo

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Login screen is missing the Ubuntu logo since the latest updates to
  kinetic.

  Looks like plymouth 22.02.122-1ubuntu2 might have triggered it.

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


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

[Desktop-packages] [Bug 1979113] Re: Kinetic sound disappeared after today updates (still trying to use pipewire-media-session)

This was fixed in ubuntu-meta 1.488 when wireplumber was introduced
(which should also uninstall pipewire-media-session).

** Package changed: pipewire (Ubuntu) => ubuntu-meta (Ubuntu)

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

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

Title:
  Kinetic sound disappeared after today updates (still trying to use
  pipewire-media-session)

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  on my laptop sound disappeared after today updates. Sound was already
  disappeared on my two desktop but I didn't know which updates to
  attribute the problem to. Today updates are:

  Start-Date: 2022-06-18  10:05:42
  Commandline: apt upgrade
  Requested-By: corrado (1000)
  Upgrade: gnome-text-editor:amd64 (42.1-1, 42.2-1), tracker:amd64 (3.3.1-1, 
3.3.1-2), libedata-book-1.2-26:amd64 (3.44.2-1, 3.44.2-2), libkeyutils1:amd64 
(1.6.1-2ubuntu3, 1.6.1-3ubuntu1), libebook-1.2-20:amd64 (3.44.2-1, 3.44.2-2), 
libecal-2.0-1:amd64 (3.44.2-1, 3.44.2-2), libedataserver-1.2-26:amd64 
(3.44.2-1, 3.44.2-2), evolution-data-server:amd64 (3.44.2-1, 3.44.2-2), 
libsnmp-base:amd64 (5.9.1+dfsg-1ubuntu2.1, 5.9.1+dfsg-4ubuntu1), 
libqt5serialport5:amd64 (5.15.4-1, 5.15.4-2), libxrender1:amd64 
(1:0.9.10-1build4, 1:0.9.10-1.1), libsnmp40:amd64 (5.9.1+dfsg-1ubuntu2.1, 
5.9.1+dfsg-4ubuntu1), evolution-data-server-common:amd64 (3.44.2-1, 3.44.2-2), 
pipewire-media-session:amd64 (0.4.1-2ubuntu2, 0.4.1-3ubuntu1), 
libglib2.0-bin:amd64 (2.72.1-1, 2.72.2-2), libqt5positioning5:amd64 
(5.15.4+dfsg-1, 5.15.4+dfsg-2), libpipewire-0.3-common:amd64 (0.3.51-1ubuntu3, 
0.3.52-1), pipewire-pulse:amd64 (0.3.51-1ubuntu3, 0.3.52-1), 
gnome-bluetooth-3-common:amd64 (42.0-5, 42.1-1), libqt5core5a:amd64 
(5.15.4+dfsg-2, 5.15.4+dfsg-3), qt5-gtk-platformtheme:amd64 (5.15.4+dfsg-2, 
5.15.4+dfsg-3), libgspell-1-common:amd64 (1.10.0-1, 1.11.1-1), 
libgtksourceview-5-common:amd64 (5.4.1-3build1, 5.4.2-1), 
libmalcontent-0-0:amd64 (0.10.4-1, 0.10.5-1), libqt5charts5:amd64 (5.15.4-1, 
5.15.4-2), libqt5script5:amd64 (5.15.4+dfsg-1, 5.15.4+dfsg-2), 
libencode-locale-perl:amd64 (1.05-1.1, 1.05-2), libqt5network5:amd64 
(5.15.4+dfsg-2, 5.15.4+dfsg-3), tracker-miner-fs:amd64 (3.3.0-1build1, 
3.3.1-1), libgspell-1-2:amd64 (1.10.0-1, 1.11.1-1), pipewire:amd64 
(0.3.51-1ubuntu3, 0.3.52-1), libqt5dbus5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), 
libsepol2:amd64 (3.4-1, 3.4-2), firefox-trunk:amd64 
(103.0~a1~hg20220612r620615-0ubuntu0.22.10.1~umd1, 
103.0~a1~hg20220615r620926-0ubuntu0.22.10.1~umd1), gir1.2-gtk-3.0:amd64 
(3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libcamel-1.2-63:amd64 (3.44.2-1, 
3.44.2-2), libglib2.0-data:amd64 (2.72.1-1, 2.72.2-2), gnome-calendar:amd64 
(42.1-1, 42.2-1), libqt5widgets5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), 
libexempi8:amd64 (2.5.2-1build1, 2.6.1-2), libqt5gui5:amd64 (5.15.4+dfsg-2, 
5.15.4+dfsg-3), libgstreamer-plugins-good1.0-0:amd64 (1.20.2-1ubuntu2, 
1.20.3-1ubuntu1), libgnome-bluetooth-3.0-13:amd64 (42.0-5, 42.1-1), 
libebook-contacts-1.2-3:amd64 (3.44.2-1, 3.44.2-2), libwoff1:amd64 
(1.0.2-1build4, 1.0.2-2), libqt5multimedia5:amd64 (5.15.4-1, 5.15.4-2), 
libedataserverui-1.2-3:amd64 (3.44.2-1, 3.44.2-2), libxtst6:amd64 
(2:1.2.3-1build4, 2:1.2.3-1.1), gir1.2-gnomebluetooth-3.0:amd64 (42.0-5, 
42.1-1), libspa-0.2-bluetooth:amd64 (0.3.51-1ubuntu3, 0.3.52-1), 
gstreamer1.0-gtk3:amd64 (1.20.2-1ubuntu2, 1.20.3-1ubuntu1), ipp-usb:amd64 
(0.9.21-1, 0.9.22-1), gstreamer1.0-plugins-good:amd64 (1.20.2-1ubuntu2, 
1.20.3-1ubuntu1), libhtml-format-perl:amd64 (2.12-1.1, 2.12-2), 
libgupnp-av-1.0-3:amd64 (0.14.0-3, 0.14.1-1), gstreamer1.0-pipewire:amd64 
(0.3.51-1ubuntu3, 0.3.52-1), enchant-2:amd64 (2.3.2-1ubuntu2, 2.3.3-1), 
pipewire-bin:amd64 (0.3.51-1ubuntu3, 0.3.52-1), libqt5svg5:amd64 (5.15.4-1, 
5.15.4-2), libglibmm-2.4-1v5:amd64 (2.66.2-2, 2.66.4-1), tracker-extract:amd64 
(3.3.0-1build1, 3.3.1-1), libgtksourceview-5-0:amd64 (5.4.1-3build1, 5.4.2-1), 
libqt5multimediawidgets5:amd64 (5.15.4-1, 5.15.4-2), libestr0:amd64 
(0.1.10-2.1build3, 0.1.11-1), libglib2.0-0:amd64 (2.72.1-1, 2.72.2-2), 
libspa-0.2-modules:amd64 (0.3.51-1ubuntu3, 0.3.52-1), 
gnome-shell-extension-ubuntu-dock:amd64 (72~ubuntu5, 72~ubuntu6), 
libgtk-3-0:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libgtkmm-3.0-1v5:amd64 
(3.24.5-1build1, 3.24.6-1), libopenmpt0:amd64 (0.6.3-1, 0.6.4-1), 
gtk-update-icon-cache:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), 
libedata-cal-2.0-1:amd64 (3.44.2-1, 3.44.2-2), libgtk-3-common:amd64 
(3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libgtk-3-bin:amd64 (3.24.33-2ubuntu1, 
3.24.34-1ubuntu1), libtracker-sparql-3.0-0:amd64 (3.3.1-1, 3.3.1-2), 
libenchant-2-2:amd64 (2.3.2-1ubuntu2, 2.3.3-1), libpipewire-0.3-modules:amd64 
(0.3.51-1ubuntu3, 0.3.52-1), inxi:amd64 (3.3.16-1-1, 3.3.18-1-1), 
libsigc++-2.0-0v5:amd64 (2.10.4-2ubuntu3, 2.10.8-1),

[Desktop-packages] [Bug 1963820] Re: Fails to act a sound server by default

This is correct (not a bug): PipeWire audio support is explicitly
disabled in 22.04 so as to avoid breaking PulseAudio there.

If you want to try PipeWire in 22.04 then the fix is indeed comment #14.

** Tags added: jammy kubuntu

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

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

Title:
  Fails to act a sound server by default

Status in pipewire package in Ubuntu:
  Invalid

Bug description:
  I understand this is quite an exotic upgrade scenario, nevertheless
  here goes: After upgrading from my pipwire enabled Kubuntu 21.10 to
  22.04 I had no usable output devices. It turns out I needed to install
  wireplumber to get my output devices back in plasma pa widget (and
  actually use them).

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


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

[Desktop-packages] [Bug 1960596] Re: no sound after upgrade to 21.10

Ubuntu 21.10 is no longer supported. Please install Ubuntu 22.04
instead.

** Changed in: pipewire (Ubuntu)
   Status: New => Won't Fix

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

Title:
  no sound after upgrade to 21.10

Status in pipewire package in Ubuntu:
  Won't Fix

Bug description:
  I had sound working in 21.04, did the mandatory upgrade to 21.10 and
  all sound is gone - in videos, browsers, games. What could be the
  problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pipewire 0.3.32-1
  ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 11 08:59:34 2022
  InstallationDate: Installed on 2020-12-21 (416 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to impish on 2022-02-10 (0 days ago)

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


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

[Desktop-packages] [Bug 1987126] Re: No audio devices are recognized

According to the attached info, the kernel does know about your audio
devices:

!!Soundcards recognised by ALSA
!!-

 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xa113 irq 127
 1 [Camera ]: USB-Audio - USB 2.0 Camera
  Sonix Technology Co., Ltd. USB 2.0 Camera at 
usb-:00:14.0-5, high speed

But I think the problem here is that PulseAudio is no used/supported in
Ubuntu 22.10. The goal is to use PipeWire instead.

So what exactly isn't working, and where?

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

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

Title:
  No audio devices are recognized

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  No audio devices are recognized, both in and out. This worked on 22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu1 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf]
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D0c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 19 11:35:58 2022
  InstallationDate: Installed on 2022-07-09 (41 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to kinetic on 2022-08-19 (0 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0904
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME H370M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Nobilis
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0904:bd09/14/2018:br5.13:svnEquusComputerSystems:pnNobilis:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH370M-PLUS:rvrRev1.xx:cvnNobilis:ct3:cvrDefaultstring:skuASUS_MB_CNL:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Nobilis
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: Equus Computer Systems

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


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

[Desktop-packages] [Bug 1987665] Re: The "Settings" app is missing the 'Appearance' option

Thank you for your bug report. According to your report you use a GNOME
upstream session

 CurrentDesktop: GNOME

The Appearance option is an Ubuntu customization and such only available
on Ubuntu sessions

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

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

** Package changed: ubuntu-settings (Ubuntu) => gnome-control-center
(Ubuntu)

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

Title:
  The "Settings" app is missing the 'Appearance' option

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

Bug description:
  In-situ upgraded V20.04LTS to V22.04.1LTS. Everything went fine.

  Ubuntu Forum users report they have an Appearance option in their
  Settings app; I don't.

  bill@bill ~$ apt show ubuntu-settings
  Package: ubuntu-settings
  Version: 22.04.6
  Priority: optional
  Section: x11
  Origin: Ubuntu
  Maintainer: Ubuntu Desktop Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 41.0 kB
  Depends: dconf-gsettings-backend | gsettings-backend, 
gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin 
(>= 2.53.4-3ubuntu1~)
  Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop
  Download-Size: 6,508 B
  APT-Manual-Installed: no
  APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  Description: default settings for the Ubuntu desktop
  This package contains the default settings used by Ubuntu.

  I wanted to move the DOCK from BOTTOM to LEFT and found no way to do
  that through Settings.

  I found what looks like the proper key/value pair in dconf Editor and
  changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I
  double checked in dconf Editor after the reboot and it says 'LEFT' but
  the dock is still at the bottom.

  BTW - this is my second attempt at trying to report this bug but
  chrome locked up the first time after I picked a .png as an
  attachment, so I'm not going to attach an image of my Settings app
  showing The 'About' along side the list of available options with
  Appearance missing from the list.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-settings 22.04.6
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Thu Aug 25 07:33:19 2022
  InstallationDate: Installed on 2021-07-21 (399 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: ubuntu-settings
  UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago)

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


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

[Desktop-packages] [Bug 1983717] Re: Monitor layout hotkey does not show single display options

2022-08-29 Thread Yao Wei

Note that https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/2056 is doing the opposite of the feature
request.

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

Title:
  Monitor layout hotkey does not show single display options

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  0) More detailed description:
  The default hotkey to switch which monitor to display the desktop on 
(Super+P) only shows two options: Mirror and Join Displays. There is no option 
"External Only" or "Built-in Only". This computer is configured with an AMD 
graphics card plugged into two external monitors, running Ubuntu 22.04 in the 
Wayland session. 

  1) lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  2) apt-cache policy gnome-shell
  gnome-shell:
Installed: 42.2-0ubuntu0.2
Candidate: 42.2-0ubuntu0.2
Version table:
   *** 42.2-0ubuntu0.2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.0-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  3) Expected to happen:
  Meta+P hotkey showing all four possibilities for display configurations 
(Mirror, Join Displays, External Only, Built-in Only).

  4) What happened instead:
  Only two options appear on screen while pressing Meta+P: "Mirror" and "Join 
Displays".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  5 09:17:19 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-01 (95 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
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland

2022-08-29 Thread Yao Wei

MR on upstream: https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/2451

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

Title:
  Monitor switcher popup (Super-P) is not displayed on desktop with
  joined display on Wayland

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Monitor switcher popup (Super-P) is not displayed on desktop with
  joined display on GNOME 3 in Wayland mode

  [Reproduce Steps]
  1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA 
GPU does not trigger the bug)
  2. Connect the PC with 2 monitors
  3. Use Super-P to switch to joined display (note that using Displays from 
Settings does not trigger the issue)
  4. Use Super-P to switch display mode again

  [Expected Result]
  Display Switcher popup should appear

  [Actual Result]
  Display Switcher does not popup, but tapping Super-P 3 times can still switch 
back to Mirror mode

  [Version]
  gnome-shell42.2-0ubuntu0.2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: gnome-shell 42.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-43-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/1984147/+subscriptions


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

[Desktop-packages] [Bug 1987737] Re: firefox from snap disabled save button in subfolders

Does it ungrey if you edit the filename? it seems a bit similar to bug
#1971516

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

Title:
  firefox from snap disabled save button in subfolders

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 22.04 fully updated
  2) Firefox snap id 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  3) I expect being able to save a file to folders in my home folder or in a 
usb drive
  4) When selecting a plugged-in USB drive or the home folder I can save, once 
I enter a subfolder the "save" button in the save dialog gets greyed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop:
   
  Date: Fri Aug 26 10:11:37 2022
  InstallationDate: Installed on 2021-07-14 (407 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (1 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-07-14T15:11:35.001074

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


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

[Desktop-packages] [Bug 1987985] Re: Totem black screen playing a video

Thank you for your bug report. Is there any error displayed on the
command line or in the journal?

Does 
$ gst-launch-1.0 playbin uri=file:///dir/to/video.avi 

has the same issue?

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Totem black screen playing a video

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Click on a video file. totem opens with a black screen.
  problem with webm, avi, mov
  totem: Installed: 43~beta-1ubuntu1
  I open the bug against totem but the bug seems open against gstreamer1.0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libgstreamer1.0-0 1.20.3-1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 17:57:01 2022
  InstallationDate: Installed on 2022-08-11 (16 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220811)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1987985/+subscriptions


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

[Desktop-packages] [Bug 1908785] Re: details view empty after browsing charge history

Thank you for your bug report, indeed that's still an issue

** Summary changed:

- gui glitch
+ details view empty after browsing charge history

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

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

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

Title:
  details view empty after browsing charge history

Status in gnome-power-manager package in Ubuntu:
  Confirmed

Bug description:
  When I click the előzmények (preliminary/previously/history) tab in
  Noteszgép akkumlátor (battery of the laptop) and then click back to
  Hálózati csatlakozó (mains power) the right hand side goes empty.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-power-manager 3.32.0-2
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 19 15:42:46 2020
  InstallationDate: Installed on 2019-11-23 (392 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: Upgraded to focal on 2020-06-03 (199 days ago)

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


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

[Desktop-packages] [Bug 1973638] Re: gnome-shell 42 leaks tens of megabytes with every screenshot

** Tags added: rjs-jj-incoming

** Tags removed: rjs-jj-incoming
** Tags added: rls-jj-incoming

** Description changed:

  [Impact]
  
  gnome-shell's memory usage grows by tens of megabytes with every
  screenshot. A few screenshots make it 100MB larger and a few dozen
  screenshots make it 1GB larger.
  
  [Test Plan]
+ 
+ THIS NEEDS CHANGING TO VERIFY THE GNOME-SHELL FIX
  
  1. Log into gnome-shell.
  
  2. Measure its real memory usage:
  
     grep RSS /proc/`pidof gnome-shell`/status
  
  3. Take 20 full screen screenshots by pressing PrtScn each time. No need
  to save them anywhere.
  
  4. Measure the memory usage again.
  
  Expected: Memory usage grows a little but growth does not exceed a few
  hundred megabytes. It should level off after a while and sometimes even
  shrink due to garbage collection.
  
  Observed: Memory usage grows without bounds, easily exceeding 1GB after
  about 20 screenshots (depending on screen resolution). It never shrinks
  significantly.
  
  [Where problems could occur]
  
  Since the fix affects GJS, problems could occur in any part of gnome-
  shell.
  
  [Other Info]
  
  This leak requires multiple fixes to minimize the memory usage. For the
  moment we are only aiming to fix the main GJS portion of the bug that
  allows memory usage to exceed 1GB.

** Description changed:

  [Impact]
  
  gnome-shell's memory usage grows by tens of megabytes with every
  screenshot. A few screenshots make it 100MB larger and a few dozen
  screenshots make it 1GB larger.
  
- [Test Plan]
+ [Test Plan for GNOME Shell Fix]
  
- THIS NEEDS CHANGING TO VERIFY THE GNOME-SHELL FIX
+ TODO
+ 
+ [Test Plan for GJS Fix]
  
  1. Log into gnome-shell.
  
  2. Measure its real memory usage:
  
     grep RSS /proc/`pidof gnome-shell`/status
  
  3. Take 20 full screen screenshots by pressing PrtScn each time. No need
  to save them anywhere.
  
  4. Measure the memory usage again.
  
  Expected: Memory usage grows a little but growth does not exceed a few
  hundred megabytes. It should level off after a while and sometimes even
  shrink due to garbage collection.
  
  Observed: Memory usage grows without bounds, easily exceeding 1GB after
  about 20 screenshots (depending on screen resolution). It never shrinks
  significantly.
  
  [Where problems could occur]
  
  Since the fix affects GJS, problems could occur in any part of gnome-
  shell.
  
  [Other Info]
  
  This leak requires multiple fixes to minimize the memory usage. For the
  moment we are only aiming to fix the main GJS portion of the bug that
  allows memory usage to exceed 1GB.

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

Title:
  gnome-shell 42 leaks tens of megabytes with every screenshot

Status in GNOME Shell:
  Unknown
Status in gjs package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gjs source package in Jammy:
  Fix Released
Status in gnome-shell source package in Jammy:
  Triaged

Bug description:
  [Impact]

  gnome-shell's memory usage grows by tens of megabytes with every
  screenshot. A few screenshots make it 100MB larger and a few dozen
  screenshots make it 1GB larger.

  [Test Plan for GNOME Shell Fix]

  TODO

  [Test Plan for GJS Fix]

  1. Log into gnome-shell.

  2. Measure its real memory usage:

     grep RSS /proc/`pidof gnome-shell`/status

  3. Take 20 full screen screenshots by pressing PrtScn each time. No
  need to save them anywhere.

  4. Measure the memory usage again.

  Expected: Memory usage grows a little but growth does not exceed a few
  hundred megabytes. It should level off after a while and sometimes
  even shrink due to garbage collection.

  Observed: Memory usage grows without bounds, easily exceeding 1GB
  after about 20 screenshots (depending on screen resolution). It never
  shrinks significantly.

  [Where problems could occur]

  Since the fix affects GJS, problems could occur in any part of gnome-
  shell.

  [Other Info]

  This leak requires multiple fixes to minimize the memory usage. For
  the moment we are only aiming to fix the main GJS portion of the bug
  that allows memory usage to exceed 1GB.

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


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

[Desktop-packages] [Bug 1987972] Re: nautilus crashed with SIGSEGV in nautilus_application_get_bookmarks

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

** Summary changed:

- nautilus crashed with SIGSEGV
+ nautilus crashed with SIGSEGV in nautilus_application_get_bookmarks

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

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

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

Title:
  nautilus crashed with SIGSEGV in nautilus_application_get_bookmarks

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Nothing to comment

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~beta.1-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:54:22 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-05-19 (100 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220518)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x557b4cd7fa15:mov0x18(%rbx),%rax
   PC (0x557b4cd7fa15) ok
   source "0x18(%rbx)" (0xfed8) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:
   file-roller   43~alpha-1
   nautilus-extension-gnome-terminal 3.45.90-1ubuntu1

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


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

[Desktop-packages] [Bug 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland

2022-08-29 Thread Yao Wei

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Yao Wei (medicalwei)

** Changed in: gnome-shell (Ubuntu)
   Status: New => 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/1984147

Title:
  Monitor switcher popup (Super-P) is not displayed on desktop with
  joined display on Wayland

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Monitor switcher popup (Super-P) is not displayed on desktop with
  joined display on GNOME 3 in Wayland mode

  [Reproduce Steps]
  1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA 
GPU does not trigger the bug)
  2. Connect the PC with 2 monitors
  3. Use Super-P to switch to joined display (note that using Displays from 
Settings does not trigger the issue)
  4. Use Super-P to switch display mode again

  [Expected Result]
  Display Switcher popup should appear

  [Actual Result]
  Display Switcher does not popup, but tapping Super-P 3 times can still switch 
back to Mirror mode

  [Version]
  gnome-shell42.2-0ubuntu0.2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: gnome-shell 42.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-43-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/1984147/+subscriptions


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

[Desktop-packages] [Bug 1987704] Re: Bulk rename Nautilus

Thank you for your bug report, the description lacks a bit of details,
is it similar to https://gitlab.gnome.org/GNOME/nautilus/-/issues/2442 ?

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2442
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/2442

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

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

Title:
  Bulk rename Nautilus

Status in nautilus package in Ubuntu:
  New

Bug description:
  Bulk rename Nautilus didn't work on Kinetic Kudu after upgraded to
  Nautilus 43

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


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

[Desktop-packages] [Bug 1987972] Re: nautilus crashed with SIGSEGV

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nothing to comment

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~beta.1-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:54:22 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-05-19 (100 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220518)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x557b4cd7fa15:mov0x18(%rbx),%rax
   PC (0x557b4cd7fa15) ok
   source "0x18(%rbx)" (0xfed8) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:
   file-roller   43~alpha-1
   nautilus-extension-gnome-terminal 3.45.90-1ubuntu1

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


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

[Desktop-packages] [Bug 1987928] Re: gnome-control-center closes with Gtk Gio Error when trying to access keyboard shortcut details

Thank you for your bug report, could you give the output of

$ dpkg -l gnome-settings-daemon-common

and then start gnome-control-center and do

$ cat /proc/`pidof gnome-control-center`/maps | grep schemas


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

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

Title:
  gnome-control-center closes with Gtk Gio Error when trying to access
  keyboard shortcut details

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

Bug description:
  Hello,

  I report this issue on behalf of someone else, I can't use the bug
  reporter on the Ubuntu machine.

  The same issue has been reported by other people on other places:

  Bug report for GNOME:
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1728

  Bug report for Debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008493

  --- lsb_release -rd ---
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  --- end lsb_release -rd ---

  --- apt-cache policy gnome-control-center ---
  gnome-control-center:
Installé : 1:41.7-0ubuntu0.22.04.4
Candidat : 1:41.7-0ubuntu0.22.04.4
   Table de version :
   *** 1:41.7-0ubuntu0.22.04.4 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:41.4-1ubuntu13.2 500
  500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:41.4-1ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  --- end apt-cache policy gnome-control-center ---

  Issue started after update of gnome-control-center on 24 August 2022
  (1:41.7-0ubuntu0.22.04.1 → 1:41.7-0ubuntu0.22.04.4)

  --- Snippet from /var/log/apt/history.log ---
  Start-Date: 2022-08-24  16:56:32
  Commandline: /usr/sbin/synaptic
  Requested-By: michel (1003)
  Upgrade: gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 
1:41.7-0ubun
  tu0.22.04.4), thunderbird:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 
1:91.13.
  0+build1-0ubuntu0.22.04.1), libpam-fprintd:amd64 (1.94.2-1, 
1.94.2-1ubuntu0.22.0
  4.1), isc-dhcp-common:amd64 (4.4.1-2.3ubuntu2.1, 4.4.1-2.3ubuntu2.2), 
thunderbir
  d-locale-en:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 
1:91.13.0+build1-0ubun
  tu0.22.04.1), thunderbird-locale-fr:amd64 
(1:91.12.0+build1-0ubuntu0.22.04.1~mt1
  , 1:91.13.0+build1-0ubuntu0.22.04.1), isc-dhcp-client:amd64 
(4.4.1-2.3ubuntu2.1,
   4.4.1-2.3ubuntu2.2), fprintd:amd64 (1.94.2-1, 1.94.2-1ubuntu0.22.04.1), 
gnome-c
  ontrol-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.4), 
gno
  me-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.4), 
thun
  derbird-locale-en-gb:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 
1:91.13.0+bui
  ld1-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 
(1:91.12.0+build1-0ubuntu0
  .22.04.1~mt1, 1:91.13.0+build1-0ubuntu0.22.04.1), 
thunderbird-gnome-support:amd6
  4 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+build1-0ubuntu0.22.04.1)
  End-Date: 2022-08-24  16:57:15
  --- end /var/log/apt/history.log ---

  The user opens gnome-control-center, the main window appears.
  The user selects the keyboard tab and click on the arrow to open the keyboard 
shortcut binding interface.

  The user expects the interface for binding keyboard shortcuts to open.

  Instead, the main gnome-control-center window closes and outputs the
  following error in the terminal:

  --- output of gnome-control-center ---

  (gnome-control-center: 647357): GLib-GIO-ERROR **: 00:31:19.451: Settings 
schema 'org.gnome.settin
  gs-daemon.plugins.media-keys' does not contain a key named 'screenshot'
  Trappe pour point d'arrêt et de trace (core dumped)
  --- end output of gnome-control-center ---

  It was working some time before the update to 1:41.7-0ubuntu0.22.04.4.

  Downgrading the package to 1:41.4-1ubuntu13.2 doesn't fix the issue.

  Regards.

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


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

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

** Tags added: nvidia

-- 
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 NVIDIA / egl-wayland:
  New
Status in GTK+:
  Fix Released
Status in egl-wayland package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 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/egl-wayland/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

One thing we changed in 22.10 is that we enabled the wpe backend, which
is the better maintained rendered and what upstream is testing. The non-
wpe codepath was even hitting errors on arm64 on recent versions as
described in https://bugs.webkit.org/show_bug.cgi?id=237636

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  On the jammy Pi desktop, under a wayland session, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

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


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

[Desktop-packages] [Bug 1987919] Re: Cannot open gnome-extension in ubuntu 22.04

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

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 1965563, 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 1965563
   gnome-extensions-app fails to start [Error reading events from display: 
Protocol error]

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

Title:
  Cannot open gnome-extension in ubuntu 22.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I've installed nvidia-driver-515 and getting this error
  Gdk-Message: 02:08:03.792: Error reading events from display: Protocol error

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


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

[Desktop-packages] [Bug 1987711] Re: Ubuntu display get shifted after some time.

Thanks. It sounds like the problem is now happening in Wayland sessions.
Since essentially the same bug was first reported in Xorg that would
make this a kernel bug.

Please try adding this line to /etc/environment:

  MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

and then reboot. It will change the way the screen is rendered in
Wayland sessions.


** Package changed: xorg-server (Ubuntu) => linux (Ubuntu)

** Summary changed:

- Ubuntu display get shifted after some time. 
+ [i915] Ubuntu display get shifted after some time.

** Tags added: i915

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

Title:
  [i915] Ubuntu display get shifted after some time.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is continuation of this bug:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583
  where advised fix was applied. 

  Summay: After ubuntu is turned on, after some time screen gets shifted
  to side. (and starts to overlap)

  I setup webcamera to record screen, and video below shows what it looked 
like. 
  after fix were applied.
  www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4
  (video was cropped, and slowed down 2x)

  before fix was applied shift looked somehow like this:
  www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4
  (video is also cropped, and slowed down 2x)

  During shift no one was present on computer.

  Is there any idea how to enable some more detailed log or something? I 
probably can pinpoint exact moment in time when shift happened. 
  i tried to read log journalctl, but I found nothing interesting.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  Date: Fri Aug 26 02:31:10 2022
  DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015]
  InstallationDate: Installed on 2022-02-17 (189 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen
   Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Default string Default string
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago)
  dmi.bios.date: 10/07/2021
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GSKU0504.V54
  dmi.board.asset.tag: Default string
  dmi.board.name: SKYBAY
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/linux/+bug/1987711/+subscriptions


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

[Desktop-packages] [Bug 1988020] Re: package speech-dispatcher 0.11.1-1 failed to install/upgrade: end of file on stdin at conffile prompt

2022-08-29 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package speech-dispatcher 0.11.1-1 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in speech-dispatcher package in Ubuntu:
  New

Bug description:
  Suddenly the issue came in although didn't find any problem running
  ubuntu so far.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: speech-dispatcher 0.11.1-1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   gir1.2-gtk-3.0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Aug 29 11:13:06 2022
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2020-10-14 (683 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.0.9
  SourcePackage: speech-dispatcher
  Title: package speech-dispatcher 0.11.1-1 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: Upgraded to jammy on 2022-08-18 (10 days ago)
  modified.conffile..etc.speech-dispatcher.modules.mary-generic.conf: [deleted]

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


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

[Desktop-packages] [Bug 1988020] [NEW] package speech-dispatcher 0.11.1-1 failed to install/upgrade: end of file on stdin at conffile prompt

2022-08-29 Thread Soham Mukherjee

Public bug reported:

Suddenly the issue came in although didn't find any problem running
ubuntu so far.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: speech-dispatcher 0.11.1-1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
AptOrdering:
 gir1.2-gtk-3.0:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Aug 29 11:13:06 2022
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2020-10-14 (683 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.0.9
SourcePackage: speech-dispatcher
Title: package speech-dispatcher 0.11.1-1 failed to install/upgrade: end of 
file on stdin at conffile prompt
UpgradeStatus: Upgraded to jammy on 2022-08-18 (10 days ago)
modified.conffile..etc.speech-dispatcher.modules.mary-generic.conf: [deleted]

** Affects: speech-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy third-party-packages

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

Title:
  package speech-dispatcher 0.11.1-1 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in speech-dispatcher package in Ubuntu:
  New

Bug description:
  Suddenly the issue came in although didn't find any problem running
  ubuntu so far.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: speech-dispatcher 0.11.1-1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   gir1.2-gtk-3.0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Aug 29 11:13:06 2022
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2020-10-14 (683 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.0.9
  SourcePackage: speech-dispatcher
  Title: package speech-dispatcher 0.11.1-1 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: Upgraded to jammy on 2022-08-18 (10 days ago)
  modified.conffile..etc.speech-dispatcher.modules.mary-generic.conf: [deleted]

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


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

[Desktop-packages] [Bug 1987409] Re: All open applications close after "screen blank" in Ubuntu 22.04 using Wayland

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

Thanks. The crash on Thu Aug 18 16:52:01 2022 is certainly bug 1969422.

The other gnome-shell crashes could not be retraced, but at least two
others look likely to be bug 1969422 as well. So I think we should point
this to bug 1969422 until a fix is ready for that.

** This bug has been marked a duplicate of bug 1969422
   gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from 
meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from 
g_set_object()

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

Title:
  All open applications close after "screen blank" in Ubuntu 22.04 using
  Wayland

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Version: 22.04
  gnome-shell Version: 42.2-0ubuntu0.2

  
  What I Expected to Happen:
  After user inactivity, computer goes into a locked state. When I log back in 
after user inactivity, all my previously opened applications are still running.

  
  What Actually Happened:
  After user inactivity, all my applications in my session are closed after 
logging back in.

  
  Details:
  This occurred on a workstation that was wiped of its previous data and Ubuntu 
22.04 installed from a flashdrive. I am getting very similar results to a bug 
in:
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987209

  
  About my system (from About menu in Settings)

  - Dell OptiPlex 3050
  - 32 GB RAM
  - Intel® Core™ i7-7700 CPU @ 3.60GHz × 8
  - AMD® Radeon rx 550 / 550 series / Mesa Intel® HD Graphics 630 (KBL GT2)
  - GNOME Version: 42.2

  Monitors being used:
  - Dell U2211Ht 22"
  - Acer G226HQL 22"
  - LG 32MA68HY 27"

  I have reproduced this error by setting the 'Screen Blank' setting to
  1 minute (just so I don't have to wait very long), then waiting for
  the system to enter the screen blank state. The following then
  happens.

  1. Everything seems to be fading out as normal
  2. Screens no longer have data that needs to be displayed, they go into sleep 
mode
  3. After a brief period, screens are forced back on (where when this problem 
isn't happening, screens will remain in sleep mode until input provided by user)
  4. System displays the dark login screen as if I was never logged in.
  5. After signing in, all my open applications have been closed.

  I have managed to circumvent this issue by choosing the option
  'Ubuntu on xorg' before signing in, or by uncommenting the line

  #WaylandEnable=false

  in /etc/gdm3/custom.conf. I then repeat the test described above after
  using either of these methods and my session is saved, no issues.

  I have attached my own results that I found after a 'journalctl -b0'.
  The text in the file are some of the lines before and after the line:

  gnome-shell[]: segfault at 

  
  Links to error reports (I got a bunch trying to replicate the issue):
  - https://errors.ubuntu.com/oops/f429c99a-2262-11ed-978c-fa163e993415
  - https://errors.ubuntu.com/oops/a07c3a5c-225e-11ed-978c-fa163e993415
  - https://errors.ubuntu.com/oops/4b027458-225c-11ed-978c-fa163e993415
  - https://errors.ubuntu.com/oops/d1cc8831-225a-11ed-978c-fa163e993415
  - https://errors.ubuntu.com/oops/cd660830-225a-11ed-b154-fa163ef35206

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 23 08:36:52 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-08-16 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1983456] Re: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04

See also Xorg bug 1986451

** Summary changed:

- Context menu options are shown under dock panel and can not be chosen on 
Ubuntu 22.04
+ Context menu options are shown under dock panel and can not be chosen in 
Wayland sessions

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

Title:
  Context menu options are shown under dock panel and can not be chosen
  in Wayland sessions

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix

Bug description:
  1. Ubuntu 22.04.1 LTS
  2. Installed packeges:
  ...
  gnome-shell-common/jammy-updates,jammy-updates,now 42.2-0ubuntu0.2 all 
[installed,automatic]
  gnome-shell-extension-appindicator/jammy,jammy,now 42-2~fakesync1 all 
[installed,automatic]
  gnome-shell-extension-desktop-icons-ng/jammy-updates,jammy-updates,now 
43-2ubuntu1 all [installed,automatic]
  gnome-shell-extension-ubuntu-dock/jammy-updates,jammy-updates,now 
72~ubuntu5.22.04.1 all [installed,automatic]
  gnome-shell/jammy-updates,now 42.2-0ubuntu0.2 amd64 [installed,automatic]

  3. Expected to choose "Property" option in right-click context menu of a 
folder in file manager.
  4. In some position of file manager's window near middle to bottom of the 
screen, the context menu was shown under dock panel without possibility to 
choose options, the dock hides menu.

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


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

[Desktop-packages] [Bug 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)

See also Wayland bug 1983456

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

Title:
  Can't click context menu items when they cover the dock (in a Xorg
  session)

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

Bug description:
  ubuntu dock in bottom position won't let me click on button (convert
  java file to Kotlin file) in android studio, but in the left position
  everything works correctly. That is, if the menu android studio
  overlaps the ubuntu dock, then the menu buttons will not be pressed.

  https://youtu.be/KsOVG7Uucow

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sun Aug 14 10:52:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed
   openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-07-13 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/gnome-shell-extension-ubuntu-dock/+bug/1986451/+subscriptions


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

[Desktop-packages] [Bug 1987134] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver

OK this sounds like an Nvidia kernel driver bug, or some other kernel
driver bug.

P.S. If you have TLP installed then please remove it as it is known to
also cause bugs like this.

** No longer affects: mutter (Ubuntu)

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

Title:
  Black screen after wake from S3 suspend on Nvidia proprietary driver

Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New

Bug description:
  An Nvidia driver upgrade in Ubuntu 20.04 caused waking from S3 suspend
  to lead to a black screen.

  Upgrading to Ubuntu 22.04 using latest stable Nvidia driver 515.65.01
  did not resolve the issue.

  There are several Nvidia sleep tickets that at first seem related, but
  mention dmesg entries that I am not seeing which makes me suspect I
  have a different issue:

  * 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970088
  * 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303

  Workaround dhenry mentions in 1970088 of disabling the nvidia suspend
  and hibernate systemd services makes no difference for me.

  Currrently running Ubuntu 22.04, Nvidia GTX 970 on driver 515.65.01,
  AMD Ryzen 7 5800X.

  Here are journalctl excerpts during the reboot process, with and
  without nvidia systemd suspend services. dmesg and /var/log/kern.log
  show no errors as are mentioned in the above tickets.

  With disabled nvidia suspend systemd services:

  Aug 19 12:42:37 uf-panacea ModemManager[2731]:   [sleep-monitor] system 
is about to suspend
  Aug 19 12:42:37 uf-panacea NetworkManager[2617]:   [1660938157.8491] 
manager: NetworkManager state>
  Aug 19 12:42:37 uf-panacea systemd[1]: Reached target Sleep.
  Aug 19 12:42:37 uf-panacea systemd[1]: Starting Record successful boot for 
GRUB...
  Aug 19 12:42:37 uf-panacea systemd[1]: Starting System Suspend...
  Aug 19 12:42:37 uf-panacea systemd-sleep[13048]: Entering sleep state 
'suspend'...
  Aug 19 12:42:37 uf-panacea systemd[1]: grub-common.service: Deactivated 
successfully.
  Aug 19 12:42:37 uf-panacea systemd[1]: Finished Record successful boot for 
GRUB.

  With enabled nvidia suspend systemd services:

  Aug 19 12:12:25 uf-panacea systemd[1]: Starting NVIDIA system suspend 
actions...
  Aug 19 12:12:25 uf-panacea suspend[15998]: nvidia-suspend.service
  Aug 19 12:12:25 uf-panacea logger[15998]: <13>Aug 19 12:12:25 suspend: 
nvidia-suspend.service
  Aug 19 12:12:25 uf-panacea systemd[1]: grub-common.service: Deactivated 
successfully.
  Aug 19 12:12:25 uf-panacea systemd[1]: Finished Record successful boot for 
GRUB.
  Aug 19 12:12:25 uf-panacea systemd[1]: Starting GRUB failed boot detection...
  Aug 19 12:12:25 uf-panacea systemd[1]: grub-initrd-fallback.service: 
Deactivated successfully.
  Aug 19 12:12:25 uf-panacea systemd[1]: Finished GRUB failed boot detection.
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"40"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event1  - 
Power Button: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"43"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event0  - 
Power Button: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"44"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event4  - 
USB Mouse OKLIC: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"45"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event5  - 
USB Mouse OKLIC Mouse: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"46"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event6  - 
USB Mouse OKLIC System Control: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"47"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event7  - 
USB Mouse OKLIC Consumer Control: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"53"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"53"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event11 - 
Valve Software Steam Controller: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"50"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"50"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event9  - 
Logitech G305: device removed
  Aug 19 12:12:25 uf-panacea rtkit-daemon[3286]: Supervising 10 threads of 4 
processes of 1 users.
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"51"
  Aug 19 12:12:25 uf-panacea

[Desktop-packages] [Bug 1970282] Re: Flatpak apps are not properly themed if a accent color other than the default is choosed

** Bug watch added: github.com/ubuntu/yaru/issues #3618
   https://github.com/ubuntu/yaru/issues/3618

** Also affects: yaru via
   https://github.com/ubuntu/yaru/issues/3618
   Importance: Unknown
   Status: Unknown

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

Title:
  Flatpak apps are not properly themed if a accent color other than the
  default is choosed

Status in Yaru Theme:
  Unknown
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  If I use any accent color other than the default orange, flatpak apps
  use the default old adwaita theme.

  These is specially obvious/important if using the dark variant of the
  theme, as the flatpak app will use a light theme.

  I attach screenshots of a flatpak app when using the default accent
  color and a different accent color, as well as the list of the
  installed yaru flatpak themes. The used accent color seems to be
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yaru-theme-gtk 22.04.4
  ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0
  Uname: Linux 5.17.0-1003-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 19:09:38 2022
  InstallationDate: Installed on 2022-02-02 (82 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: yaru-theme
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (38 days ago)

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


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

[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit

The Yaru team would be unaware of this bug because it is still closed
for the Yaru project. I'll reopen it now, but someone please also report
the issue to the Yaru design team at
https://github.com/ubuntu/yaru/issues and then mention the new issue ID
here.


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

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

Title:
  Dark themes don't work well with highlighted current line in gedit

Status in GtkSourceView:
  Fix Released
Status in gtksourceview4 package in Ubuntu:
  Triaged
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  In order to checkout out an old bug report I started gedit, enabled
  "Highlight current line" and changed the application theme to "Yaru-
  dark" The current line is highlighted correctly but the text is
  unreadable because it is too light. The text needs to be much darker.

  This is not a theme that I would normally use so I'm not too bothered
  about how the problem is fixed but this configuration makes gedit very
  difficult to use as you can't actually see the text that you're
  adding, changing or deleting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: yaru-theme-gtk 19.10.4
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 21 16:33:03 2019
  InstallationDate: Installed on 2019-05-17 (218 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  PackageArchitecture: all
  SourcePackage: yaru-theme
  UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago)

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


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

[Desktop-packages] [Bug 1804568] Re: [HP Spectre x360 Convertible 13] click position is flipped to cursor position when in tent mode

Alright we can declare the bug fixed then. Although it might just be
because of the switch to Wayland by default. Does the bug occur on jammy
if you select 'Ubuntu on Xorg' from the login screen?

** Changed in: mutter (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  [HP Spectre x360 Convertible 13] click position is flipped to cursor
  position when in tent mode

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  same bug is present 18.04 and 18.10:

  after I log in in tent mode the screen goes upside down, and after

  xrandr --output eDP-1 --rotate normal

  it goes back to normal however now the cursor is upside down, and
  click position and cursor position isnt the same, they are flipped

  thank you for the fix in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: coreutils 8.28-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 04:28:21 2018
  ExecutablePath: /bin/sleep
  InstallationDate: Installed on 2018-11-22 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANG=hu_HU.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1950 F pulseaudio
   /dev/snd/controlC1:  imi1950 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.31
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.60
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13-w0XX
  dmi.product.sku: Z9E46EA#ABV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1333 F pulseaudio
   /dev/snd/controlC1:  imi1333 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-23 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.49
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.71
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV

[Desktop-packages] [Bug 1980170] Re: Tapping on the current app's icon in the dock (via touchscreen) doesn't show the current windows (while clicking it does)