Nevermind. The gnome-shell fix was reverted upstream because it is
incorrect.
** Tags removed: rls-jj-incoming
** Changed in: gnome-shell (Ubuntu)
Status: Fix Committed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed t
> OpenBLAS blas_thread_init: pthread_create failed for thread 7 of 16:
Resource temporarily unavailable
16 threads is not much so that alone isn't the issue. However
https://github.com/xianyi/OpenBLAS/issues/1668 mentions that the
offending code might have set the stack ulimit to gigabytes in size
** Package changed: totem (Ubuntu) => openblas (Ubuntu)
** Summary changed:
- Video thumbnails fail to generate
+ totem-video-thumbnailer fails in OpenBLAS blas_thread_init
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubu
Yeah it sounds like too many threads are created to get around the 30
second limit when -l is not used.
--
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/1988100
Title:
totem-video-thum
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, abou
** Summary changed:
- Video thumbnails fail to genetate
+ Video thumbnails fail to generate
--
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/1988100
Title:
Video thumbnails fail to ge
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 thi
> 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 thi
> 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 cr
** 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
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
--
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
** 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
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
stallationDate: 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=(c
stalled 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
*** This bug is a duplicate of bug 1966418 ***
https://bugs.launchpad.net/bugs/1966418
The workaround for bug #1966418 doesn't work for me.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpa
*** This bug is a duplicate of bug 1966418 ***
https://bugs.launchpad.net/bugs/1966418
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evolution (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ub
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 Konfigur
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
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
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 encount
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
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 encount
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
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 unavaila
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 notifica
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 bu
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 r
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: ubun
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1983717
T
You have been subscribed to a public bug:
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
S
MR on upstream: https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/2451
--
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/1984147
Title:
Monitor switcher popup (Super-P)
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
** 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 l
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
** 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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https
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 (Ubun
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1987972
Title:
nautilus crashed with SIGSEGV
To manage notifications about this
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 rece
** Tags added: nvidia
--
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/1965563
Title:
gnome-extensions-app fails to start [Error reading events from
display: Protocol error]
T
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
*** 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
43 matches
Mail list logo
