[Bug 1966795] Re: First boot with fingerprint auth enabled, gdm doesn't prompt to enter password

2022-12-13 Thread Francois Thirioux
my laptop: ThinkPad P14s
Bus 005 Device 002: ID 06cb:00bd Synaptics, Inc. Prometheus MIS Touch 
Fingerprint Reader

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

Title:
  First boot with fingerprint auth enabled, gdm doesn't prompt to enter
  password

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966795] Re: First boot with fingerprint auth enabled, gdm doesn't prompt to enter password

2022-12-13 Thread Francois Thirioux
Hi all,

I run into the same issue (Jammy, GDM).
Sometimes I get pwd and fp auth, sometimes fp *then* pwd. Very random.

Very annoying since a fp gdm auth causes GS to ask for pwd to open
seahorse keys wallet pwd after session startup.

Logs:

07:48:17 gdm3: Gdm: Child process -1900 was already dead.
07:48:17 gsd-color: failed to connect to device: Failed to connect to missing 
device 
/org/freedesktop/ColorManager/devices/xrandr_Chimei_Innolux_Corporation_gdm_126
07:48:17 gdm-session-wor: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT 
(object)' failed
07:48:17 gnome-shell: Registering session with GDM
07:48:14 gdm-session-wor: gkr-pam: gnome-keyring-daemon started properly and 
unlocked keyring
07:48:14 gdm-session-wor: gkr-pam: gnome-keyring-daemon started properly and 
unlocked keyring
07:48:14 gdm-session-wor: pam_unix(gdm-password:session): session opened for 
user fthx(uid=1000) by (uid=0)
07:48:14 gdm-session-wor: gkr-pam: stashed password to try later in open session
07:48:14 gdm-session-wor: gkr-pam: unable to locate daemon control file
07:48:10 gdm-session-wor: gkr-pam: no password is available for user
07:48:06 gnome-shell: Registering session with GDM
07:48:04 systemd: Started Session c1 of User gdm.
07:48:04 (systemd): pam_unix(systemd-user:session): session opened for user 
gdm(uid=126) by (uid=0)
07:48:04 systemd-logind: New session c1 of user gdm.
07:48:04 gdm-session-wor: pam_unix(gdm-launch-environment:session): session 
opened for user gdm(uid=126) by (uid=0)


07:48:41 systemd: fprintd.service: Deactivated successfully.
07:48:08 fprintd: libusb: error [udev_hotplug_event] ignoring udev action change
07:48:06 dbus-daemon: [system] Successfully activated service 
'net.reactivated.Fprint'
07:48:06 fprintd: Device responded with error: 789 retry: 1
07:48:06 dbus-daemon: [system] Activating via systemd: service 
name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.34' 
(uid=126 pid=1938 comm="/usr/bin/gnome-shell " label="unconfined")

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

Title:
  First boot with fingerprint auth enabled, gdm doesn't prompt to enter
  password

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1975557] Re: blank screen does not turn off display backlight

2022-12-13 Thread Casonade
I have the same problem. Screen Blank activates after a period of
inactivity and then the monitor briefly turns off then on with
backlight. Fresh install OS does not fix the problem. Can someone help?

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

Title:
  blank screen does not turn off display backlight

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1999335] Re: Please remove vte from Ubuntu

2022-12-13 Thread Jeremy Bicha
It can't be removed from Debian until someone ports debian-installer
away from GTK2. :(

** Tags removed: lucid
** Tags added: lunar

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

Title:
  Please remove vte from Ubuntu

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1915910] Re: evince does not print (apparmor, pxgsettings)

2022-12-13 Thread Brian Murray
Hello Togo28, or anyone else affected,

Accepted evince into kinetic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/evince/43.0-1ubuntu1
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-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. 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.

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

** Tags added: verification-needed verification-needed-kinetic

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

Title:
  evince does not print (apparmor, pxgsettings)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1999578] [NEW] Bursts of high CPU usage after triggering overview

2022-12-13 Thread Esokrates
Public bug reported:

As requested in the upstream bug report
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137, I hereby file
the downstream issue:

I am experiencing high cpu usage of gnome-shell in situations where I
would not expect it, leading to my fans running more often and wasting
my battery on my Dell XPS 13 9310 2-in1.

The problem can be seen in action here: 
https://www.youtube.com/watch?v=Y9o7a7BGPE4
See also the upstream report for syscap recordings of such situations.

I think there might be a correlation with firefox being opened on
another workspace (but no video or any other playback happening). At
least everytime I notice that my an comes on for no reason and I fire up
top to see gnome shell consuming too much cpu, when I kill all my
firefox windows gnome shell cpu usage goes down as well, but that could
be pure coincidence.

At least I can safely rule out the triple buffering downstream ubuntu
mutter patch, since I recompiled mutter without the patch and it does
not really change the problem much.

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


** Tags: kinetic

** Attachment added: "apport.gnome-shell.4sllnc5r.apport"
   
https://bugs.launchpad.net/bugs/1999578/+attachment/5635523/+files/apport.gnome-shell.4sllnc5r.apport

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

Title:
  Bursts of high CPU usage after triggering overview

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3

2022-12-13 Thread Jeremy Bicha
Marc, 102.6 was officially released today, so I've gone ahead and
updated my jammy mozjs branch for it. I added the CVEs you mentioned and
found one more I found from 102.4. I don't see any new ones for 102.6

I've also created a ubuntu/102/kinetic branch for mozjs102 for kinetic.
Since it doesn't have the gjs major update issue, I believe it could be
pushed sooner than jammy.

For Jammy, I think the general plan is for this update to be built in
security-proposed and then published/copied to jammy-proposed for wider
testing before being pushed to jammy-security.

My understanding is that the Ubuntu Desktop and Ubuntu SRU teams have
come to an agreement that we will test all the gnome-shell extensions
that are available in the official Ubuntu repositories (for 22.04 LTS
and later). Extensions installed outside of the official Ubuntu
repositories are unsupported, just like anything that is user-installed
outside of Ubuntu. However, we aren't aware of any likely breakage for
any GNOME Shell extensions caused by this proposed update.

There is no formal API for GNOME Shell extensions which allows
extensions to have tremendous power but it's easily possible for an
extension to break GNOME Shell so that it's not possible for GNOME Shell
to run correctly or even start.

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

Title:
  [jammy] Update gjs to 1.74 using mozjs102 102.3

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled

2022-12-13 Thread Huan Zhang
I have the same issue with the latest gnome-shell-extension-ubuntu-dock - 
74ubuntu2
It's related to display scaling, using 200% has this issue. In my case I need 
to use display scaling otherwise the texts are extremely small on my screen.

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

Title:
  gnome-shell search can't launch apps if dock auto-hide is enabled

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1971126] Re: unable to click on application search results

2022-12-13 Thread Huan Zhang
*** This bug is a duplicate of bug 1979096 ***
https://bugs.launchpad.net/bugs/1979096

I have the same issue, disabling all extensions does not help.
The bug appears when auto-hide is on, so basically makes auto-hide unusable.

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

Title:
  unable to click on application search results

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754477] Re: totem crashed with SIGSEGV in memcpy() from gen8_render_init() from i965_Init() from __vaDriverInit_1_0()

2022-12-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  totem crashed with SIGSEGV in memcpy() from gen8_render_init() from
  i965_Init() from __vaDriverInit_1_0()

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754477] Re: totem crashed with SIGSEGV in memcpy() from gen8_render_init() from i965_Init() from __vaDriverInit_1_0()

2022-12-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  totem crashed with SIGSEGV in memcpy() from gen8_render_init() from
  i965_Init() from __vaDriverInit_1_0()

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore

2022-12-13 Thread Sam Brightman
This release was made specifically to help out older LTS distributions
which cannot migrate to newer libgweather. What needs to be done to get
it into 20.04?

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

Title:
  (Update libgweather to 3.36.2) Weather forecast and info is not
  available anymore

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1999335] Re: Please remove vte from Ubuntu

2022-12-13 Thread Steve Langasek
It should be removed, but this package is synced from Debian.  File a
removal request there?

(BTW, 'lucid' is the wrong tag by 13 years ;)

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

Title:
  Please remove vte from Ubuntu

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs