I'
--
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/1870278
Title:
Shell is unresponsive at the lock screen for ~10s after unlocking
To manage notifications about this bug go to
*** This bug is a duplicate of bug 1857191 ***
https://bugs.launchpad.net/bugs/1857191
** Changed in: gedit (Ubuntu)
Importance: Undecided => Low
** This bug has been marked a duplicate of bug 1857191
Dark themes don't work well with highlighted current line in gedit
--
You received t
I've *disabled* all extensions; this is with no (non-Ubuntu-system)
extensions enabled. (Now up to 400MB RSS) ☺
--
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/1870278
Title:
Sh
sounds similar to bug #1711377
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1867806
Title:
why when i create an icon on the desktop that if goes behin
Thank you for your bug report. In what directory do you try to open the
.desktop? What permissions does it have? Could you add a screenshot
showing the issue?
** Changed in: nautilus (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
On 20.04,the .desktop file could not show correct icons and open by
correct applications.
It only show a 'setting' icon, and when you double click it, it will use
gedit to open it.
nautilus 1:3.36.1-1ubuntu1
** Affects: nautilus (Ubuntu)
Importance: Undecided
I have tried, and will try again, to understand how extensions and
JavaScript in general are able to use so many megabytes so quickly...
--
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/
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https:/
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https:/
No, it doesn't start that high on login. The desktop is currently at
370MB RSS in a fairly fresh X11 session (now that Shell actually starts
again after I removed all the extensions 🤦)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gn
Tracking in
https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba
but see also
https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002
** Description changed:
+ https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba
+ https://errors.ubu
*** This bug is a duplicate of bug 1870454 ***
https://bugs.launchpad.net/bugs/1870454
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
3.36.0-2ubuntu2, the problem page
** Changed in: snap-store
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1866998
Title:
Snap Store snap can be uninstalled using Snap Store
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
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.ne
*** This bug is a duplicate of bug 1870454 ***
https://bugs.launchpad.net/bugs/1870454
** This bug has been marked a duplicate of bug 1870454
gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0)
from meta_monitor_config_manager_assign()
--
You received this bug noti
*** This bug is a duplicate of bug 1870454 ***
https://bugs.launchpad.net/bugs/1870454
** This bug has been marked a duplicate of bug 1870454
gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0)
from meta_monitor_config_manager_assign()
--
You received this bug noti
*** This bug is a duplicate of bug 1870454 ***
https://bugs.launchpad.net/bugs/1870454
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
3.36.0-2ubuntu2, the problem page
** Summary changed:
- gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs()
+ gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0)
from meta_monitor_config_manager_assign()
** Information type changed from Private to Public
--
You received this bug notification b
Please attach a photo or video of the problem so we can get a better
idea.
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
*** This bug is a duplicate of bug 1870354 ***
https://bugs.launchpad.net/bugs/1870354
** Summary changed:
-
/usr/bin/gnome-shell:11:st_theme_node_get_text_align:_st_set_text_from_style:st_label_style_changed:_g_closure_invoke_va:g_signal_emit_valist
+ gnome-shell crashed with SIGSEGV in st_
It looks like the offending caller might be:
https://github.com/mlutfy/hidetopbar/blob/master/intellihide.js#L93
so please try removing that hidetopbar extension.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
You have been subscribed to a public bug:
When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the
ubuntu terminal window flickering between a white filter on it, and the
terminal's normal appearance.
This happens whenever I run "ubuntu-bug" and the window asking me for
more infor
Looks like a pretty rare problem. 2 occurrences in focal and 4 in xenial...
https://errors.ubuntu.com/problem/6289ea5c593afc5b43d7c38e671ae741c8f66fcf
** Description changed:
+ https://errors.ubuntu.com/problem/6289ea5c593afc5b43d7c38e671ae741c8f66fcf
+
+ ---
+
Seems to be happening when dock
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
3.36.0-2ubuntu2, the problem page at
https://errors.ubuntu.com/problem/6289ea5c593afc5b43d7c38e671ae741c8f66fcf
contains mor
*** This bug is a duplicate of bug 1865300 ***
https://bugs.launchpad.net/bugs/1865300
** This bug is no longer a duplicate of private bug 1870380
** This bug has been marked a duplicate of bug 1865300
gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
g_hash_table_looku
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 1869470
When reporting bugs in the future please use apport by using 'ubuntu-
bu
This should only happen if your dock is set to automatically hide. Is
that set?
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
desktop-icons (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-exte
Public bug reported:
Gedit with Ubuntu Dark-Theme and Tango shows white fonts on white
background when the line is highlighted (current line). Attached image
exemplifies it.
The expected behaviour is to have a darker background with white fonts,
or darker fonts with white background.
To fix it i
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1867806/+attachment/5345233/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1867806/+attachment/5345234/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
http
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1867806/+attachment/5345235/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.lau
apport information
** Tags added: apport-collected
** Description changed:
when I create an icon on the desktop it goes behind the launcher
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu21
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease:
** Changed in: gnome-keyring (Ubuntu)
Importance: High => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1870053
Title:
gnome-keyring ftbfs in focal
To manage notific
We also shouldn't be able to remove core, core18, snapd or the various
content snaps that other snaps depend on like:
gnome-3-26-1604
gnome-3-28-1804
gnome-3-34-1804
gtk-common-themes
gtk2-common-themes
kde-frameworks-5-core18
kde-frameworks-5-qt-5-14-core18
--
You received this bug notification
** Changed in: snap-store
Assignee: Ken VanDine (ken-vandine) => Robert Ancell (robert-ancell)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1866998
Title:
Snap Store snap can b
*** This bug is a duplicate of bug 1870380 ***
https://bugs.launchpad.net/bugs/1870380
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 #1870380, so is being marked as such.
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1845801
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
I have the same issue on a fresh install of the Focal Beta.
Using a GTX1060 with any proprietary drivers (I tested 440, 435, 390)
breaks autologin.
Removing "splash" from /etc/default/grub and doing "sudo update-grub"
fixes it.
--
You received this bug notification because you are a member of U
** Description changed:
I have a paired bluetooth device listed as "Disconnected" in the
Bluetooth section of gnome-control-center. In order to connect to it I
click on the device name and switch the "Connection" slider to the "on"
position. The slider moves but immediately bounces back to
Public bug reported:
GIMP 2.10.8 crashes for me when selecting any theme, or reloading the
current theme.
Steps to reproduce:
(1) Open The GIMP.
(2) Open Preferences.
(3) Open theme selection in preferences.
(4) Select any theme, OR click "reload current theme".
(5) Crash.
See bug information be
It has been reported upstream as well
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/925
It seems the bluetooth panel is generating activity (through
sharing/discovery enablement probably) which create access conflicts...
https://www.reddit.com/r/gnome/comments/flpy74/does_anyone_e
Thanks for the detail. I think if you had let blueman out of the
description and focussed on the actual issue the bug would have been
easier to understand but I think I understand what you describe now
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 1869124 ***
https://bugs.launchpad.net/bugs/1869124
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 #1869124, so is being marked as such.
Thanks Sebastien. I already know uninstalling blueman doesn't help as I
did install it exactly because I couldn't connect to the bluetooth
device with gnome-control-center. I was pretty surprised to see it
worked.
bluetoothctl behaves exactly like blueman-manager: does not work if
gnome-control-ce
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1870356/+attachment/5344959/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://b
apport information
** Tags added: apport-collected focal third-party-packages uec-images
wayland-session
** Description changed:
I have a paired bluetooth device listed as "Disconnected" in the
Bluetooth section of gnome-control-center. In order to connect to it I
click on the device name
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1870356/+attachment/5344958/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubu
Thank you for your bug report, could you try to uninstall blueman and
see if it works better with the default installation software?
Can you connect the device from bluetoothctl when you get the issue from
gnome-control-center?
Could you add your 'journalctl -b 0' log to the bug after getting the
More data points:
- When I try to connect from gnome-control-center, this error is logged:
bluetoothd[1635]: connect error: Device or resource busy (16)
- Connecting *fails* from blueman-manager if gnome-control-center is
open at the Bluetooth section at the same time. The same error is
logged.
If I unpair ("remove") the device using blueman-manager, it will
correctly show up in the gnome-control-center Bluetooth settings as "Not
Set Up". If I click on it, it *does* pair and connect. I can also
successfully disconnect from the device from gnome-control-center, but
can not reconnect, as ex
** Tags added: champagne
--
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/1870356
Title:
Can't connect to paired bluetooth devices via g-c-c; works with
blueman
To ma
Public bug reported:
I have a paired bluetooth device listed as "Disconnected" in the
Bluetooth section of gnome-control-center. In order to connect to it I
click on the device name and switch the "Connection" slider to the "on"
position. The slider moves but immediately bounces back to the "off"
Thanks for confirming!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1870053
Title:
gnome-keyring ftbfs in focal
To manage notifications about this bug go to:
https://bugs.
it now successfully built after the second retry. So sometimes failing
...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1870053
Title:
gnome-keyring ftbfs in focal
To mana
Could you give it a retry?
Debian reported it upstream but it seems random and not always failing
(in which case it's still good to see fixed but maybe not a rls blocker)
https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/55
** Bug watch added: gitlab.gnome.org/GNOME/gnome-keyring/-/issues #
*** This bug is a duplicate of bug 1857736 ***
https://bugs.launchpad.net/bugs/1857736
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 #1857736, so is being marked as such.
Thanks for considering it, Sebastien. I submitted an upstream merge
request:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/732
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
http
The flickering is not a bug, it's a feature. The flickering is meant to
happen and if you don't want it then please turn off visual bell/alerts.
However it kind of sounds like it might not be working reliably. If you
think that's the case then please report the issue to the upstream
developers at:
I don't think that's reasonable. My personal threshold for reasonable is
around 500MB, given on login it's only:
~240MB for an Ubuntu session
~170MB for a vanilla GNOME session
And has been that way for a couple of cycles at least.
So yes I think 650MB RSS sounds like a bug... unless it star
Shell memory usage is reasonable at 650MB RSS. NVIDIA isn't being used.
--
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/1870278
Title:
Shell is unresponsive at the lock screen f
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1869122
Title:
mutter 3.36.0-2ubuntu1 changelog incorrectly
So, when I clicked the 'Test' button the first time, it blanked for a
longer time before coming back on, but after that, it flickered very
shortly.
Also, assuming that the problem is related to this feature, I think that
then it would blank out every time any alerts came in. However, it
blanks out
https://salsa.debian.org/gnome-team/gnome-shell/-/merge_requests/38
** Summary changed:
- Ubuntu logo vanishes and fades back in (with a slightly different size) on
gdm start
+ Ubuntu logo vanishes and fades back in on gdm start
--
You received this bug notification because you are a member o
https://salsa.debian.org/gnome-team/mutter/-/merge_requests/59
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
D
I'm the developer of desktop icons. I have a patch waiting review that
should fix this at https://gitlab.gnome.org/World/ShellExtensions
/desktop-icons/-/issues/190
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-
Sorry, the patch is at https://gitlab.gnome.org/World/ShellExtensions
/desktop-icons/-/merge_requests/166
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/18
If the problem gets worse over time then it might be memory related.
Please run:
ps auxw | grep gnome-shell
and tell us what you see when it is (a) fast and (b) slow.
If that's the problem then it is likely an extension is to blame. So
make sure you have uninstalled ALL of them, at least tempo
Also check your gnome-shell memory and CPU usage. This is starting to
sound like bug 1869568.
--
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/1870278
Title:
Shell is unresponsiv
Please also attach a full kernel log (dmesg). Because if nvidia-
drm.modeset is active that's something we need to know and tag.
** 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
Update: my spare PC is definitely getting slower at unlocking, but
(possibly because I'm not using it as much) not as quickly.
Are there any logs/debug steps you want me to run on it? I know enough
gdb to be dangerous, if that helps.
--
You received this bug notification because you are a member
Tracking in: https://gitlab.gnome.org/GNOME/mutter/issues/349
But maybe we should use:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1151
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1151
https://gitlab.gnome.org/GNOME/mutter/-/issues/1151
--
You received this bug notificatio
It appears this problem is unique to Ubuntu. It doesn't happen in
vanilla GNOME without extensions.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2557
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2557
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/
BTW, I can't seem to reproduce any such problems.
--
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/1870278
Title:
Shell is unresponsive at the lock screen for ~10s after unlockin
73 matches
Mail list logo
