** Description changed:
When I select the task bar menu, click on the Wifi and select "Select to
network", a modal window appears that allows me to select a Wifi
network.
- Normally, when I click Cancel or Connect, the modal window disappears
- and returns me to the desktop.
+ After I
Public bug reported:
When I select the task bar menu, click on the Wifi and select "Select to
network", a modal window appears that allows me to select a Wifi
network.
After I have clicked on one of the networks, normally, when I click
Cancel or Connect, the modal window disappears and returns
The new mutter fixes things for me too, thanks for the quick turnaround
(Wayland still has some annoying issues)
--
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/1917926
Title:
Public bug reported:
In Wayland, some maximized windows such as gnome-terminal and Eclipse
get moved to behind the dock when the screensaver is unlocked, ie the
window starts maximized and drawn next to the dock, but after locking
and unlocking the screen it is now behind the dock (see attached
*** This bug is a duplicate of bug 1917926 ***
https://bugs.launchpad.net/bugs/1917926
Yep, I'd say it's that bug. It's fine under Wayland.
In 21.04 will it be possible to select a Wayland session from the login
screen without commenting out the gdm rule that disables Wayland if the
nvidia
*** This bug is a duplicate of bug 1917926 ***
https://bugs.launchpad.net/bugs/1917926
** Description changed:
- After a recent update in 21.04, I can no longer move windows by clicking
+ After a recent update in 21.04, I can no longer move windows with
+ integrated title bars (eg nautilus,
Public bug reported:
After a recent update in 21.04, I can no longer move windows by clicking
on the taskbar and dragging. I can't resize them either - although the
mouse icon changes, when I click and move the mouse the window doesn't
resize.
I can move a window holding the Super key and
I think this might be fixed now - g-c-c hasn't updated, but I am seeing
the dropdowns for resolution and primary display now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Also may be of interest: if I set either laptop or external monitor to a
non-native resolution, I do get a dropdown for the screen set to non-
native resolution and can change the resolution in g-c-c.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Perhaps of interest: if I set the primary monitor to the external
monitor via xrandr and then run g-c-c, g-c-c shows a dropdown that
allows me to select the laptop monitor as primary. Then if I close g-c-c
and re-run it, the dropdown doesn't appear any more.
--
You received this bug notification
Thanks Sebastien: reverting to gnome-settings-daemon 3.36.1-1ubuntu2
(and rebooting) fixed all the hotkey issues for me.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
@Geziel: well, Ubuntu 20.10 *is* a development version, so you expect
some bugs. It is normally more usable at this stage of the development
cycle, though.
FWIW, I ran evtest, and the keys are mostly being reported the same in
groovy and focal - they just don't work in groovy. eg the function
Public bug reported:
The Ubuntu 20.10 version of g-c-c lacks the dropdown controls for
changing screen resolution or selecting the primary monitor. Where there
is normally a dropdown, there is just a label showing the current screen
resolution or primary monitor. In some cases the dropdown is
PrtScr and Alt-PrtScr are also not working for me. (Alt-F2 does work,
though.)
--
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/1893579
Title:
Ctrl + Alt + T and Fn keys not
FWIW, in Ubuntu 20.10 you can't change the resolution of the external
monitor with g-c-c at all, because there is no dropdown for the
resolution, just a label showing the current resolution.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I reported it here: https://gitlab.gnome.org/GNOME/mutter/-/issues/1402
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1402
https://gitlab.gnome.org/GNOME/mutter/-/issues/1402
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
@Daniel: That current mode is from the xrandr.txt when the working
2560x1440 resolution is set. Lionel and I got the 23.98 Hz figure from
monitors.xml that I generated after the 1920x1080 change is applied and
the monitor has no signal. With the monitor receiving no signal in
1920x1080, the
But why does g-c-c choose the lowest frequency refresh instead of the
highest? If I set the resolution to 1920x1080 using xrandr, it chooses
the 60 Hz option:
1920x1080 60.00* 50.0059.9430.0025.0024.00
29.9723.98
which is this modeline:
1920x1080 (0xbc) 148.500MHz
This is monitors.xml after changing to the (non-working) 1920x1080
configuration. It seems to have chosen a refresh rate of
23.976079940795898 Hz (is that the last option in xrandr's modeline
"1920x1080 60.0050.0059.9430.0025.0024.00
29.9723.98"?).
When I use xrandr to
This is after changing to the (working) 2560x1440 resolution.
** Attachment added: "monitors-2560x1440.xml"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5405199/+files/monitors-2560x1440.xml
--
You received this bug notification because you are a
No, that doesn't help - the screen stays blank if I set it to 1920x1080
using g-c-c and then run the set max bpc command.
I also tried setting 1920x1080i using xrandr in case that's what g-c-c
was choosing but it worked fine.
With the 1920x1080 setting chosen in g-c-c (and the monitor
** Attachment added: "xrandr.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5404255/+files/xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
It doesn't work in Wayland, either.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5404254/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5404256/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Public bug reported:
g-c-c is unable to change the resolution on my external 2560x1440
monitor to 1920x1080 - when I try, the monitor turns off.
However, the command "xrandr --output HDMI-1 --mode 1920x1080" does
successfully change the resolution.
xrandr for the monitor shows:
HDMI-1
My Ubuntu 20.04 installation just did this - something changed the
org.gnome.desktop.lockdown disable-lock-screen to true and also the
blank screen to never (did an update do this?).
But there's nothing I can see in gnome-control-center to modify this
value, making this bug pretty obscure when it
Ok, I've reported it as bug #1871554.
--
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/1849249
Title:
gnome-shell crashed with SIGABRT:
Do you mean I should recreate this exact same bug and then report it as
another one?
--
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/1849249
Title:
gnome-shell crashed with
Do you mean a link to the original crash? This one has the same date as
the bug report:
https://errors.ubuntu.com/oops/4bb4a564-f475-11e9-b5e5-fa163e102db1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "Output of journal -b0"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+attachment/5348700/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Oh, I spoke too soon. I tested it yesterday and it passed, but today it
failed. I had geany on the primary monitor this time.
** Changed in: gnome-shell (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
This is fixed for me in gnome-shell 3.36.0-2ubuntu2, thanks!
--
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/1849249
Title:
gnome-shell crashed with SIGABRT:
I think this might be fixed in gnome-shell 3.36.0-2ubuntu2 - I can't
reproduce my duplicate bug https://bugs.launchpad.net/bugs/1868418
anymore.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
It looks like it's fixed here in gnome-shell 3.36.0-2ubuntu2, thanks.
--
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/1868896
Title:
Minimized windows reappear when closing the
How quickly is Ubuntu likely to be refreshed with the fix? I don't mind
minimized windows pseudo-reappearing after the overview screen closes,
but they also do the same on every right mouse click in many apps, and
then it's a right pain when you keep clicking on them and wonder why
they aren't
This doesn't happen with every application, eg right-clicking in
Firefox, nautilus, and gnome-terminal demonstrates the bug, but right-
clicking in google-chrome doesn't.
Also, the behaviour is slightly different in Wayland vs X11 - in X11 I
can't interact with the backgrounded window's titlebar
Public bug reported:
In today's update of Ubuntu 20.04, if I do this:
* Run Firefox non-maximized
* Run another app (eg nautilus or gnome-terminal)
* Minimize the other app
* Right-click on the firefox window
then the other app suddenly re-appears. You can only interact with its
titlebar,
Still happens every time in gnome-shell 3.36.0-2ubuntu1 / geany
1.36-1build1.
--
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/1849249
Title:
gnome-shell crashed with SIGABRT:
I know we're not supposed to comment on this bug, but this is just to
quickly note that almost all of the issues I noted in comment #7 have
disappeared now in gnome-shell 3.36.0-2ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Extensions are pretty badly buggy for me on Focal. Some work, but many
don't, and won't upgrade, can't be configured, and don't give any
information about why they have failed.
If I go to https://extensions.gnome.org/, the installed extensions page
tells me that there are extensions like
This is still 100% reproducible with with an up-to-date Ubuntu 20.04.
--
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/1849249
Title:
gnome-shell crashed with SIGABRT:
: Installed on 2019-07-01 (112 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/rocko
ProcEnviron:
LANG=en_AU.UTF-8
LANGUAGE=en_AU:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_R
The snap version was the only version available in 19.04, and it doesn't
run for me in 19.10, but I see there's a non-snap version now available
in 19.10 that does run.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calculator
I just discovered that on my laptop this bug only applies to X11
sessions, not to Wayland sessions.
--
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/1849249
Title:
gnome-shell
@jagosta: does it only crash if the dialogs are on different monitors?
That's what I find.
FWIW, I tried the live USB, but ootb Ubuntu 19.10 doesn't recognise the
HDMI monitor, so I can't do dual displays, and I also tried a VirtualBox
guest, but even after installing Ubuntu 19.10 and guest
Public bug reported:
On a VirtualBox 6.0.14 host, with a fresh install of Ubuntu 19.10 and
the virtualbox guest drivers installed, I can't configure a second
display, although xrandr shows it to be present.
Steps:
1. Install VirtualBox
2. Install Ubuntu 19.10 as a guest with 2 displays (note:
Here's the xrandr. It looks like 0x0 is selected for display Virtual2
and maybe this is confusing g-c-c.
** Attachment added: "xrandr"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1851189/+attachment/5302626/+files/xrandr
--
You received this bug notification because
I also removed solaar, which had an indicator (but I think it's showing
through app-indicators), with no luck.
I also tried changing the screen configuration to laptop on the left,
monitor on the right, and the bug is still present.
--
You received this bug notification because you are a member
I removed all those extensions (and mate-optimus as well), so
~/.local/share/gnome-shell/extensions/ is completely empty, but the bug
is still there.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
t; - Alpha amd64 (20190606)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/rocko
ProcEnviron:
LANG=en_AU.UTF-8
LANGUAGE=en_AU:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
Signal: 6
SourcePackage: g
I think it's fixed now, so closing.
--
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/1842882
Title:
gnome-control-center no longer shows all the xrandr resolutions
To manage
I think it's resolved now.
** Changed in: mutter (Ubuntu)
Status: New => Invalid
--
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/1842882
Title:
gnome-control-center no
Even with the POP OS! PPA removed, this is still happening. Sometimes
the resolutions are all there and sometimes not.
** Changed in: mutter (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I think this might have been caused by the Pop OS! PPA
(ppa:system76/pop). I think I must have installed it months ago for some
icon set without realising that it loads a ton of other stuff. Its
latest iteration of g-c-c segfaults, which is how I realised what was
going on. Purging the PPA and
This bug is still an issue with mutter 3.34.0-3ubuntu1. Is there any
more info I can provide?
--
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/1842882
Title:
gnome-control-center no
Public bug reported:
Very recently the ubuntu-dock has started displaying some right-click
menus for pinned apps on the wrong monitor. It doesn't happen for all
the apps, but when it does, the menu is permanent but you can't click on
it and you have to restart gnome-shell with ALT-F2 'r' (which
After resuming from suspend, the extra resolutions have disappeared from
g-c-c (but are still available via xrandr), so something is still
triggering the bug.
** Changed in: gnome-control-center (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a
Looks like it's fixed now.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Invalid
--
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/1842882
Title:
A side-effect of this is that after resuming, gnome-shell will have
often (but not always) reverted to a different resolution from the one
set when it suspended.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
Ok, I know what has happened. In Disco the default shell theme has dark
topbar menus (and light popup windows eg ALT F2) so the topbar menus are
always dark. But now in Eoan the topbar menus have changed to always be
"light". See the attached screenshot, where I have selected "Try Ubuntu"
from the
For me the best solution would be if Ubuntu shipped with a yaru-dark
shell theme so you could make the desktop visually consistent out-of-
the-box. But that's just my 2 cents... when I suggested this in another
bug report about the system pop-up boxes, it wasn't received with any
enthusiasm!
--
But user themes *is* installed and *is* working - here's a screenshot of
gnome-tweaks/Extensions showing the user themes extension with no
exclamation mark. It most definitely is working, because I can change
the themes (application and shell themes) to my user-installed ones.
I think the user
** Summary changed:
- gnome-shell top bar menus no longer honour dark theme settings
+ gnome-shell top bar menus no longer honour application theme settings, eg
dark themes
** Description changed:
- When you selected a dark theme, the gnome-shell top bar menus used to
- also switch to match
I already had the user themes extension installed (and in gnome-tweaks,
it says user themes are turned on and have no errors). I didn't have the
gnome-shell-extensions package, but installing it doesn't fix the bug.
Note that if I choose a dark user them for the shell, it does change the
toolbar
Public bug reported:
When you selected a dark theme, the gnome-shell top bar menus used to
also switch to match the theme (ie light text on a dark background) - eg
see the screenshot showing the top-bar calendar at
https://micheleg.github.io/dash-to-dock/news/2015/03/01/approaching-
Public bug reported:
Very recently gnome-control-center started only showing a subset of the
available screen resolutions. I'll attach a screenshot and also the
xrandr dump to show what I mean, eg you can see that the 2048x1152
(16:9) resolution is now missing.
ProblemType: Bug
DistroRelease:
** Attachment added: "Output from xrandr"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1842882/+attachment/5286922/+files/xrandr
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
I can still manually apply resolutions from the command line, eg "xrandr
-s 2048x1152" changes the screen resolution correctly.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Thanks, mutter 3.32.2+git20190711-2ubuntu1 fixes it for me in eoan.
--
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/1834583
Title:
[eoan][regression] GNOME Shell hangs when closing
FWIW, if this is the same as bug #1835033, I find it only hangs when you
close a dialog of a dialog - closing a first-level dialog of the main
program seems to be ok.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Did launchpad auto-fill in the bug title? I don't remember typing in
"spinning" or any of the rest of the text, but maybe I'm just going mad!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I did that and it is reported as bug #1835033.
When I killed the frozen gnome-shell process, it had recovered by the
time I switched back to it and I was then able to close the offending
window.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Also in case it's of any help, I only have Ubuntu's default gnome-shell
extensions running.
--
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/1834984
Title:
gnome-shell freezes
Hmm. I did that, and eventually it asked if I wanted to send a report,
so I said yes ('S' for send), and then nothing happened except it
created a zero-length file /var/crash/_usr_bin_gnome-
shell.0.7619.hanging. A bit later I got a window saying that a report
was ready to send, so I told it to
That command gives me "apport-cli: error: -u/--update-bug option cannot
be used together with options for a new report".
Should I omit the -u option and create a new bug?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
Public bug reported:
Whenever I run Netbeans 11 (using either openjdk11) and (eg):
1. Open Tools / Plugins.
2. Go to Settings.
3. Click on 'Add'.
4. Click 'Cancel'.
then gnome-shell freezes (except for the mouse), apparently indefinitely
(I have left it for 30+ minutes.)
I can login as another
Public bug reported:
If I launch (eg) nautilus from gnome-terminal, the address bar gets
focus so I can press CTRL-L to immediately start typing in an directory
path, and if I launch (eg) gnome-calculator from gnome-terminal, the
data entry field gets focus so I can start typing in a calculation.
I haven't noticed it happening in 18.10 or 17.04.
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Invalid
--
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/1613711
I think these issues are all fixed in 19.04 except that gnome-shell
stores screen configurations in different places for Wayland and X.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
@Daniel: I still see this bug occasionally in 18.10 and 19.04. When it
happens, the ubuntu dock and the status bar still work, but none of the
applications will accept any input, including gnome-terminal. You can
switch applications using the dock, but alt-tab doesn't do anything, and
ALT-F2
It's still an issue in Ubuntu 18.04 and 18.10. g-c-c should really
prompt the user to install gnome-online-accounts if it is not installed
instead of pretending to work and then failing.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Ok, ps does show a /usr/sbin/gdm3 process running in cosmic.
The extra session that loginctl used to show is this one (shown from
bionic):
29033 tty1 Ssl+ 0:00 /usr/lib/gdm3/gdm-wayland-session gnome-
session --autostart /usr/share/gdm/greeter/autostart
and this is no longer running on
Ok, so it looks like this is intended behaviour, ie to save memory? When
I first reported the bug, gdm3 didn't reappear when I switched to tty1,
but now it reappears after five seconds or so of showing a blank screen.
It then dies shortly after I switch back to tty2. It's just a pity it
takes so
This is pretty easy to reproduce: the latest daily build (Oct 4) of
cosmic does it on first reboot after installation in a VM: as on my
system, loginctl shows only a single session present. There are no crash
files in /var/crash, and there are no errors logged at ubuntu.com.
Is this expected
There aren't any crash files and there aren't any relevant errors at
errors.ubuntu.com. I can't apply the workaround from bug #994921 because
there is no line with problem_types in /etc/apport/crashdb.conf to
comment out.
--
You received this bug notification because you are a member of Ubuntu
:
$ loginctl
SESSION UID USER SEAT TTY
2 1001 rocko seat0 tty2
1 sessions listed.
There's no crash file in /var/crash, and no useful information in gdm3's
status:
$ systemctl status gdm3
● gdm.service - GNOME Display Manager
Loaded: loaded (/lib/systemd/system/gdm.service; static
Just for completeness, there have been no more crashes with Removable
Drive Menu enabled, so it is likely that System Monitor was the culprit.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
If you change the ownership of files in /home/ to another user,
you can no longer log into 's gnome-shell session - instead, you
are either returned to the gdm login screen or the computer locks up.
This is even the case if .config and .local and .cache are completely
empty.
So far there have been no lockups since I disabled those two, so I've
re-enabled Removable Drive Menu to see if that causes the lockups to
return.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Ok, I have started by disabling Removable Drive Menu and System Monitor
and so far, so good. (But since it's random, it might take a while to
reproduce anyway.)
So gnome-shell doesn't enforce any sort of timeout for non-responsive
extensions?
--
You received this bug notification because you
I don't think there's anything particularly unusual about my home
folder. I formatted the root partition as btrfs instead of ext4 when I
did the installation, so the Ubuntu installer put /home into its own
subvolume. I also asked the installer to encrypt the home folder, so
it's encrypted with
I finally managed to generate a crash file - see bug #1781647.
--
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/1730540
Title:
gnome-shell freezes after resume then unlock
To
It keeps locking at inconvenient times when I can't get access to
another PC, which is why I'm having trouble providing crash logs.
It was fine suspending/resuming for the last week and a half and then
crashed this morning. The only difference was that I applied updates
last night before I
I managed to build and install a patched gjs last night thanks to a
helpful hint from a fellow user (ie to use debuild -us -uc -b to build
it instead of make and make install).
Initially, gnome-shell was using around 170 MB according to gnome-
system-monitor (atop says consistently says it is
Well, quite. I built and installed it with "./configure --prefix=/usr &&
make && sudo make install" and it's obviously more complicated than
that. Is there a guide somewhere for how to build and install gnome-
shell and its components in ubuntu?
--
You received this bug notification because you
Is that patch getting into Ubuntu soon? I tried applying it to the
latest gjs source package and installing the patched package, but it
left gdm in an un-startable state, even when I uninstalled it and
reinstalled the default gjs package.
--
You received this bug notification because you are a
I sometimes find that not only mouse clicks get blocked, but everything
except ubuntu-dock and the Activities overview stops accepting input. (I
can't ALT-F2 to restart gnome, and I can't ALT-tab between apps.) On a
couple of occasions I found that it was a single app that had captured
input (and
It's still happening every now and again.
** Changed in: gnome-shell (Ubuntu)
Status: Expired => 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.net/bugs/1730540
Title:
@Berg: your bug sounds like this one -
https://bugzilla.gnome.org/show_bug.cgi?id=780167
** Bug watch added: GNOME Bug Tracker #780167
https://bugzilla.gnome.org/show_bug.cgi?id=780167
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
It wasn't due to nvidia-drm.modeset=0. gdm still works with that absent
from the boot parameters.
It could be a fix in gdm3, which is now at 3.27.92-0ubuntu1. But
https://launchpad.net/ubuntu/+source/gdm3/ suggests that was released
over a week ago, and this problem was definitely still present
1 - 100 of 573 matches
Mail list logo
