@daniel thanks for the tip!
Disabling seems to solve the focus issue, but now there's no more
desktop icons (duh :) )
Personally I use the desktop icons all the time, anything that needs
immediate attention goes to the desktop, disabling that would (for me)
not be a workaround, but a choice betwe
** Tags added: jammy
** Tags added: i18n l10n
** Changed in: gnome-session (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1973476
*** This bug is a duplicate of bug 1942238 ***
https://bugs.launchpad.net/bugs/1942238
** This bug is no longer a duplicate of private bug 1945430
** This bug has been marked a duplicate of bug 1942238
gnome-session-binary crashed with SIGSEGV in g_signal_emit_valist() from
g_signal_emit_b
*** This bug is a duplicate of bug 1942238 ***
https://bugs.launchpad.net/bugs/1942238
** This bug is no longer a duplicate of private bug 1945430
** This bug has been marked a duplicate of bug 1942238
gnome-session-binary crashed with SIGSEGV in g_signal_emit_valist() from
g_signal_emit_b
** 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 gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1942238
Title:
gnome-session-binary crashed with SIGSEGV in g_signal_emit_va
*** This bug is a duplicate of bug 1942238 ***
https://bugs.launchpad.net/bugs/1942238
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-session. This problem was most recently seen with package version
42.0-1ubuntu2, the problem page
*** This bug is a duplicate of bug 1942238 ***
https://bugs.launchpad.net/bugs/1942238
** This bug has been marked a duplicate of bug 1942238
gnome-session-binary crashed with SIGSEGV in g_signal_emit_valist() from
g_signal_emit_by_name() from
gsm_exported_client_private_emit_query_end_se
Sounds like a tricky problem because Desktop Icons NG is itself an
application that is allowed to take focus (when appropriate).
** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubun
Tracking in
https://errors.ubuntu.com/problem/2ef5aa580d895d1745829490f213cec85c99e9c2
** Information type changed from Private to Public
** Description changed:
+ https://errors.ubuntu.com/problem/2ef5aa580d895d1745829490f213cec85c99e9c2
+
unknown reason for crash
ProblemType: Crash
D
Tracking in:
https://errors.ubuntu.com/problem/7d04bae8b01fc69d3c8db64f88f8b01331c7f327
** Description changed:
+ https://errors.ubuntu.com/problem/7d04bae8b01fc69d3c8db64f88f8b01331c7f327
+
This is happening since the first boot after upgrading to 21.10
ProblemType: Crash
DistroRelease
Thanks Gunnar. The reason the string was picked is to be able to reuse
the translations from gnome-shell, which made sense at this point of the
cycle, but is it really the best string to use for Ubuntu? Upstream
doesn't have a dock but we do, perhaps we should use 'pin to dock' for
our shell? Proba
Please also check for crashes:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
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/1973397
Also tracking in https://gitlab.gnome.org/GNOME/mutter/-/issues/2276
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2276
https://gitlab.gnome.org/GNOME/mutter/-/issues/2276
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Then somehow in between 21.10 and 22.04 there was a change in the
behaviour of Desktop Icons NG, as in: when is grabbing focus
appropriate.
If the new behaviour is preferred by the author, it would be nice for
the end-user to have the option to toggle between the old and the new
behaviour.
--
Yo
*** This bug is a duplicate of bug 1971516 ***
https://bugs.launchpad.net/bugs/1971516
Can confirm the bug is fixed in gtk4 4.6.3
--
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/
I doubt the new behaviour is preferred by the author or anyone. Seems
like a mistake. Please report it to:
https://gitlab.com/rastersoft/desktop-icons-ng/-/issues
** No longer affects: gnome-shell (Ubuntu)
** Summary changed:
- no auto-focus application after workspace switch
+ Desktop Icons NG
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2287
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5414
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5414
** Changed in: gnome-shell
Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5488 =>
gitlab
** Changed in: mutter
Remote watch: gitlab.gnome.org/GNOME/mutter/-/issues #2258 =>
gitlab.gnome.org/GNOME/mutter/-/issues #2276
--
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/1
Public bug reported:
After resume from suspend. Gnome shell is lagging and takes 100% of one
of the cpus
I see the following in the logs
aj 16 10:33:12 graf sudo[745687]: pam_unix(sudo:session): session closed for
user root
maj 16 10:33:15 graf gnome-shell[200033]: Window manager warning:
last_
I have looked in ~/.local/share/gnome-shell/ There is no extensions
folder. This is a new install of Ubuntu 22.04 with no modifications yet.
Here is the ls output of the folder ~/.local/share/gnome-shell/
drwx-- 2 richard richard 4.0K May 16 07:24 .
drwx-- 23 richard richard 4.0K May 15 1
Thank you for your bug report. The string was translated after the
current language packs were generated so is missing from the curent
version
https://translations.launchpad.net/ubuntu/jammy/+source/gnome-
session/+pots/gnome-session-42/fr/29/+translate
it should be fixed in the next langpacks re
Would be nice if someone having the issue would report it upstream,
https://gitlab.gnome.org/GNOME/totem/-/issues , without user description
nor someone to provide details a report isn't probably going to be of
much use
** Changed in: totem (Ubuntu)
Importance: Undecided => High
--
You receiv
Looks like a difference of 11ms, so less than one frame.
This is most likely to be a buggy app (or toolkit) as the message
suggests. Please try to identify what the offending app is. For example
if the window ID is still 0xae then:
xwininfo -id 0xae
or
xprop -id 0xae | grep _NET
Thank you for your bug report. Indeed, the image can be opened in gimp
or shotwell viewer so seems one to report upstream to
https://gitlab.gnome.org/GNOME/eog/issues
** Changed in: eog (Ubuntu)
Importance: Undecided => Low
** Changed in: eog (Ubuntu)
Status: New => Confirmed
--
You r
Since the cause of gnome-shell leaks is almost never gnome-shell itself
I am unassigning that package.
** Package changed: gnome-shell (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://b
** Summary changed:
-
/usr/bin/totem:11:___pthread_mutex_destroy:g_rec_mutex_impl_free:g_rec_mutex_clear:gst_video_decoder_finalize:g_object_unref
+ totem crashed with SIGSEGV in ___pthread_mutex_destroy() from
g_rec_mutex_impl_free() from g_rec_mutex_clear() from
gst_video_decoder_finalize() f
This looks like a related question https://github.com/micheleg/dash-to-
dock/issues/1705
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1705
https://github.com/micheleg/dash-to-dock/issues/1705
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs
Public bug reported:
[Impact]
When testing native messaging support with the firefox snap (not yet
released, see https://github.com/flatpak/xdg-desktop-portal/pull/705),
gnome-shell won't prompt the user for permission to authorize a given
extension to access the portal, because the app id being
Hmm.. Using "Pin to Dock" (via a gnome-shell patch I suppose) may be
better. Doing so probably lets us keep the established "Dock" and still
be consistent.
Changing this bug accordingly.
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-contro
The reason why I bring up this early is that we are about to document
Ubuntu differences in the desktop guide. So for both docs and
translation reasons: Let's do this soon, and avoid some last minute UIF
break.
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
--
You receive
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: gnome-shell (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https:/
** Changed in: gnome-shell (Ubuntu Jammy)
Status: Triaged => 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://bugs.launchpad.net/bugs/1968911
Title:
assertion failures in cr_parser_ne
Public bug reported:
Since ubuntu-drivers-common 1:0.9.0~0.20.04.6,
system running kernel 5.4 & nvidia-340 will experience
10s useless delay on boot because
gpu-manager is waiting for nvidia-drm to load
& nvidia-drm is not built in with nvidia-340.
Several legacy nvidia cards are stuck to nvidia
Thanks, just opened a separate bug:
[nvidia340] display hangs 10s on boot with nvidia-340
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1973604
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpa
** Package changed: gdm3 (Ubuntu) => ubuntu-drivers-common (Ubuntu)
--
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/1973604
Title:
[nvidia340] display hangs 10s on boot with nvidia-340
If we go this route, we'll need yet another conditional in dash-to-dock.
Adding gnome-shell-extension-ubuntu-dock as affected package.
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Thank you for your bug report. That's probably worth reporting upstream
on https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues
Unsure it is changing the mount option, when selecting as an user it can
map to the user who did the action but for a system mount that's not
possible. The UI could
Using 70~ubuntu3.21.10.1 there is no freeze and the previews are correct
** Tags removed: verification-needed verification-needed-impish
** Tags added: verification-done verification-done-impish
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subsc
Finally got the crashdump uploaded but had to add all the details to a
new ticket: LP#1973615
--
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/1972812
Title:
gnome-shell (X11, nv
Using 3.44.1-0ubuntu1 evolution works fine, tested email and calendar
and played a bit with the options without issue
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a me
*** This bug is a duplicate of bug 1972812 ***
https://bugs.launchpad.net/bugs/1972812
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1965897, so is being marked as such.
Yes, I've tried evolution 3.44.1-0ubuntu1 too and it works well.
I'm going to temporarily drop the verification-done tags because I want
evolution-data-server 3.44.1 to be fully phased in jammy-updates first.
** Tags removed: verification-done-jammy
** Tags added: verification-needed-jammy
--
Y
Okay, so it turns out that the implementation wrapper also doesn't pass
the value.
** Also affects: xdg-desktop-portal (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "xdg-desktop-portal-1.6.0-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/
Public bug reported:
I have configured the hotspot to automatically start at startup. The
hotspot correctly starts on startup, but it appears to be configured
incorrectly. No device connected to it can reach the internet. When
opening the settings, Wifi is indicated to be disabled, even though the
Public bug reported:
Used the "compress" function from the context menu of the Nautilus
browser. When an attempt is made to select a compression type, part of
the dialog is obscured...had to guess at it, to get the job done.
(screenshot is attached)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
P
Public bug reported:
i running wine program and i want doing a lot screenshot. after did it
and close program. my system very laggy. i see at htop program my ram
and swap full.
my system info.
Host: mantari Kernel: 5.17.7-xanmod1 x86_64 bits: 64 compiler: gcc
v: 11.2.0 parameters: BOOT_IMAGE
*** This bug is a duplicate of bug 1967480 ***
https://bugs.launchpad.net/bugs/1967480
** This bug has been marked a duplicate of bug 1967480
GUI error in "compress file". Menu content is wider than menu window.
--
You received this bug notification because you are a member of Ubuntu
Desk
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1736
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1971415
Title:
Remote desktop is automatically en
The problem is, if you want a partition to be auto-mounted, you either must
edit the fstab or THE INSTRUCTIONS are to turn off the "default" mounting in
gnome disk utility and it will auto-mount. However, the auto-mounting is done
as system root and I don't have access to it. So I must google
This bug was fixed in the package gnome-shell - 42.1-0ubuntu1
---
gnome-shell (42.1-0ubuntu1) kinetic; urgency=medium
* New upstream release (LP: #1973373, LP: #1968911)
* Drop patches applied in new release
-- Jeremy Bicha Fri, 13 May 2022 16:32:49 -0400
** Changed in: gnome
This bug was fixed in the package gnome-shell - 42.1-0ubuntu1
---
gnome-shell (42.1-0ubuntu1) kinetic; urgency=medium
* New upstream release (LP: #1973373, LP: #1968911)
* Drop patches applied in new release
-- Jeremy Bicha Fri, 13 May 2022 16:32:49 -0400
** Changed in: gnome
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
42.0-2ubuntu1, the problem page at
https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058
contains more
*** This bug is a duplicate of bug 1965897 ***
https://bugs.launchpad.net/bugs/1965897
** This bug is no longer a duplicate of bug 1972812
gnome-shell (X11, nvidia-390) crashes with SIGSEGV when unlocking the screen
** Description changed:
- Could be a duplicate of LP1972812
-
ProblemT
Comment #14 is not related to this bug. Please ignore it.
--
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/1972812
Title:
gnome-shell (X11, nvidia-390) crashes with SIGSEGV when
This is a duplicate of bug 1962823 which itself is too vague. Although
it seems most reports of it from jammy are bug 1970917.
--
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/19736
It looks like you have copied someone else's log from an unrelated bug?
That shows bug 1717170 and bug 1965820. We don't need to discuss those
here.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.la
gnome-shell (42.1-0ubuntu1) kinetic; urgency=medium
* New upstream release (LP: #1973373, LP: #1968911)
* Drop patches applied in new release
-- Jeremy Bicha Fri, 13 May 2022 16:32:49 -0400
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-shell
gnome-shell (42.1-0ubuntu1) kinetic; urgency=medium
* New upstream release (LP: #1973373, LP: #1968911)
* Drop patches applied in new release
-- Jeremy Bicha Fri, 13 May 2022 16:32:49 -0400
** Changed in: gnome-shell (Ubuntu)
Status: Fix Committed => Fix Released
** Also affects:
gnome-shell (42.1-0ubuntu1) kinetic; urgency=medium
* New upstream release (LP: #1973373, LP: #1968911)
* Drop patches applied in new release
-- Jeremy Bicha Fri, 13 May 2022 16:32:49 -0400
** Changed in: gnome-shell (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: gn
gnome-shell (42.1-0ubuntu1) kinetic; urgency=medium
* New upstream release (LP: #1973373, LP: #1968911)
* Drop patches applied in new release
-- Jeremy Bicha Fri, 13 May 2022 16:32:49 -0400
** Changed in: gnome-shell (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: gn
I'm not sure I agree with this, but do appreciate the wording is
confusing in a world of dash and dock.
* Regular users are less likely to understand "pinned" as much as "favourites".
* Power users may have no dock, only a dash, and so the existing wording is
correct.
* It's a patch we would have
The screenshot in comment #1 shows gnome-shell is only 168MB resident.
So no leak there.
Please run:
ps auxw > psoutput.txt
free -h > free.txt
lspci -k > lspci.txt
journalctl -b0 > journal.txt
and attach the resulting text files here.
I suspect there is no leak here and we should instea
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1973638
When reporting bugs in the future please use apport by using 'ubuntu-
Public bug reported:
See upstream: https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/159
Would be nice to see a backport in jammy.
(Note: even though the upstream bug is in evolution-ews, the fix is in
evolution: https://gitlab.gnome.org/GNOME/evolution/-/commit/5065d763f8)
** Affects: evol
** Description changed:
gnome-shell crashes with SIGSEGV just after logging:
gnome-shell[3117]: JS ERROR: TypeError: window is null
_destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9
_initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16
Examples:
htt
65 matches
Mail list logo
