After this update, Gnome Shell ignores /org/gnome/desktop/interface
/text-scaling-factor setting on start. Gnome Shell always starts with
scaling 1.0. When I rewrite this setting manually Gnome Shell accepts it
and scale interface correctly.
My laptop uses FHD resolution on 11" display, so I use t
Not only nvidia, I have this issue on intel laptop. See my comment here
-
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/comments/10
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpa
Cristiano Nunes (cfgnunes) wrote:
"I have two computers here, the bug occur with only the computer with NVIDIA
card."
I have same issue on intel laptop with intel graphics.
But I not use gdm, I use lightdm and x11 session.
Maybe using gdm hides this issue on non-nvidia as gdm starts in wayland
m
It's normal behaviour.
Dot appear only after some amount of time and/or if there many unread
notifications.
If you wish immediate notification you may install Notifications Alert
extension - https://extensions.gnome.org/extension/258/notifications-
alert-on-user-menu/
--
You received this bug n
No fix in proposed for bionic yet?
Updated libmutter/gnome-shell from proposed, commented
WaylandEnable=false in /etc/gdm3/custom.conf - still black screen on
Fujitsu M2010 netbook.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutt
Same bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720219
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1722298
Title:
keyboard autorepeat not happening when I
Same issue on Lenovo Flex 14 laptop and 17.10.
--
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/1711538
Title:
Tap-to-click does not work on the GDM login screen
To manage notification
Public bug reported:
Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu.
Looks like same issue in upstream -
https://bugzilla.redhat.com/show_bug.cgi?id=1651952
Workaround - use previous version of libgnome-desktop-3-17 without bubblewrap.
ProblemType: Bug
DistroRelease: Ubuntu 18.
** Attachment added: "Output of 'ps -fA'"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1809660/+attachment/5224651/+files/ps-fA.txt
--
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/b
Public bug reported:
Sometimes, when user start new session, gdm session may spawn several
times.
Example:
- System started, gdm session at tty1.
- User eugene enter. Eugene session at tty2.
- User vladik start new session from locked screen. Vladik session at tty4,
and, unexpected, second gdm s
** Summary changed:
- When starting new user session, gdm session may start twice or thrice
+ When starting new user session, new gdm3 session may spawn
** Summary changed:
- When starting new user session, new gdm3 session may spawn
+ When starting new user session, new gdm session may spawn
-
But why? Looks like gdm bug.
--
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/1809660
Title:
When starting new user session, new gdm session may spawn
To manage notifications about thi
With this update was landed in bionic, layout indicator issue arisen:
After screen unlock, layout indicator doesn't show layout letters (en, ru,
etc).
See attached pic.
Also, when clicked to layout indicator, in drop down menu no layout selected
with dot.
Layout letters appears after switching
Same here, after latest gjs/polkit bionic updates about once per day
this issue happens. Syslog contains some .js blames about polkit
(attached).
** Attachment added: "syslog-err.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+attachment/5231470/+files/syslog-err.log
Yesterday this happens again, symptoms exactly as described in Bug
Description: "When the screen is locked manually (by clicking the lock
screen icon), the screen either freezes with the desktop still showing".
Say again, this started after latest gjs/polkit updates was landed in
bionic.
syslog a
I not have this extension, but have the issue...
But anyway, I dropped using gdm and use lightdm + gnome-screensaver + extension
to fix lock button behaviour.
Looks like gnome shell behaves better without gdm.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs
Public bug reported:
Calling Power-Off dialog from system menu and then pressing cancel
button terminates some apps like fbreader and telegram. Tested on Ubuntu
18.04 and 19.10.
Steps to reproduce:
1. Install fbreader from standard repository (sudo apt install fbreader)
2. Run fbreader
3. Press G
"The power off dialog is meant to ask apps if they can, or to try to,
close" - but not before I confirmed the action.
"or a bug in the app itself" - yes, it's most likely.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
Just add syslog messages on pressing power off button in gnome shell
menu:
Oct 21 09:49:11 eugene-VirtualBox gnome-shell[3241]: endSessionDialog: No
XDG_SESSION_ID, fetched from logind: 6
Oct 21 09:49:12 eugene-VirtualBox gnome-session-binary[3226]: Entering running
state
Oct 21 09:49:12 eugene-
Public bug reported:
gnome-shell under 'gdm' user most of time eats more CPU than any other
real user process.
'top' screenshot attached, see first line, most CPU eating and time
consuming process.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSigna
After receiving updates to gnome-shell (now 3.26.2, was 3.26.1) and
reboot issue not observed anymore. So I close bug.
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Just to note: Looks like I can see this gdm/gnome-shell CPU eating on a
test install of just updated Ubuntu 18.04 (XOrg mode) in VirtualBox.
--
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.
After upgrading artful to bionic (debian way, replaced artful to bionic in
sources.list) faced this issue.
Solved by installing libegl-mesa0 package.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launc
Public bug reported:
Gnome Shell disables extensions on screen lock.
If, for example, new mail will arrived in Thunderbird during screen locked, no
badges will be shown on unlock.
Also, lock/unlock screen while badges displayed will clear them.
So, in current implementation, badges looks very un
It little bit hard to distinguish active tab from inactive tabs in
Nautilus.
For example, in Adwaita theme, current tab underlined with theme
selection color and clearly visible. Please add such pronounce in
Ambiance/Radiance.
** Tags added: bionic nautilus tabs
--
You received this bug notific
Digged little bit into gtk3 css-ing and created workaround:
Add to ~/.config/gtk-3.0/gtk.css:
.nautilus-window notebook tab:checked {
background-image: linear-gradient(to top, @selected_bg_color,
alpha(@bg_color, 0) 3px);
}
Active tab will be underlined with theme color. Remove ".nautilus-
*** This bug is a duplicate of bug 1759621 ***
https://bugs.launchpad.net/bugs/1759621
** Description changed:
- gnome-shell crashed when I attach USB drive or phone with storage.
+ gnome-shell crashes when I attach USB drive or phone with storage.
ProblemType: Crash
DistroRelease: Ubu
For me (Bug #1760588) gnome-shell crashes nearly always when I attach
USB drive or phone with storage.
--
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/1759621
Title:
gnome-shell
After my patch when I try to reproduce crash, nautilus says:
nautilus[19488]: gtk_stack_set_visible_child_name: assertion 'GTK_IS_STACK
(stack)' failed
But at least it not crashed and looks usable without fear about "oh, all
my file manager windows is gone".
--
You received this bug notificatio
> tags: added: focal noble
Can't confirm issue on focal or noble, only on jammy.
I tried simple dirty patch:
---
--- nautilus-42.6.orig/src/nautilus-gtk4-helpers.c
+++ nautilus-42.6/src/nautilus-gtk4-helpers.c
@@ -113,7 +113,10 @@ gtk_widget_get_first_child (GtkWidget *w
{
g_autoptr (GList)
To reproduce gnome-shell crash under Xorg:
- Start "Ubuntu on Xorg" session
- Run some apps (gnome-shell probably will not crash if no apps/windows opened)
- Try to restart gnome-shell with usual way (Alt-F2 - r - Enter, repeat if not
crashed)
See: https://askubuntu.com/questions/1522417/getting
Public bug reported:
Maximized GTK 2 apps does not restore maximized state when run under
"Ubuntu on Xorg" session in 24.04 and 24.10.
Steps to reproduce:
- Install gtk 2 app which saves windows state, e.g. GIMP.
- Start GIMP. Maximize GIMP window. Close GIMP.
- Start GIMP again.
Result:
GIMP
After two weeks of intensive use of the patched nautilus, I think this
patch is production ready. No side effects (for me).
** Patch added: "bug-2011350.patch"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011350/+attachment/5840872/+files/bug-2011350.patch
--
You received this bu
> it feels like more of a workaround
Yes, but as I stated in comments #16 and #17, it much better than
nothing, as with it Nautilus in jammy become usable. Without this patch
it just crashed on any active use (more than one window and more than
one tab per window) under X11 environment.
Also, dig
proposed on salsa.debian.org
--
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/2011350
Title:
ERROR:../src/nautilus-gtk4-helpers.c:116:gtk_widget_get_first_child:
assertion failed:
GNOME's README on gitlab clearly states "Only the latest version of Files as
provided upstream is supported".
So, I thinks there is no point to propose patch into upstream.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in
When such affected application maximized, gnome-shell says in log:
gnome-shell[1540]: Can't update stage views actor unnamed [MetaSurfaceActorX11]
is on because it needs an allocation.
gnome-shell[1540]: Can't update stage views actor unnamed [MetaWindowActorX11]
is on because it needs an alloca
** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu)
--
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/2087951
Title:
GTK 2 apps does not remember maximized state (Xorg ses
--
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/2087951
Title:
GTK 2 apps does not remember maximized state (Xorg session) in noble
and oracular
To manage notifications about
While packages not yet in proposed, I downloaded it from build page
(version 1:42.6-0ubuntu2) and confirm this package fixes the bug for me.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.l
40 matches
Mail list logo