Importing setuptools in a python interpreter works fine:
rocko@ubuntu:~$ python3
Python 3.10.2 (main, Feb 26 2022, 08:21:15) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> try:
... import setu
is:
rocko@ubuntu:~$ pip install pathlib
Defaulting to user installation because normal site-packages is not writeable
Collecting pathlib
Downloading pathlib-1.0.1.tar.gz (49 kB)
━━━ 49.3/49.3 KB 117.3 kB/s eta 0:00:00
Preparing metadata (setup.py) ... error
Just a note that the duplicate bug
https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1960280 has a
workaround, which is to install the version of libserf-1-1 from 21.10
(you also have to pin it to stop apt from updating it automatically).
--
You received this bug notification because you
*** This bug is a duplicate of bug 1956040 ***
https://bugs.launchpad.net/bugs/1956040
** This bug has been marked a duplicate of bug 1956040
Malformed TLS handshake with OpenSSL 3.0 (breaks subversion)
** Summary changed:
- subverion's svn fails against https servers
+ subversion's svn
The problem seems to be in libserf. If I install the 21.10 version of
libserf with dpkg from
http://archive.ubuntu.com/ubuntu/pool/universe/s/serf/libserf-1-1_1.3.9-10_amd64.deb,
subversion starts working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Ubuntu 21.10 and 22.04 have exactly the same reported version of svn
(1.14.1) and the plugin that handles https, ra_serf (version 1.3.9).
However, 21.04 reports it was compiled on Feb 18 2021, while 22.04
reports it was compiled on Dec 3 2021.
On both my 22.04 VM and my 22.04 wsl running under
Thanks for looking so quickly. I'm almost certain the problem will go
away without the nvidia driver because the nouveau driver didn't
recognise the hardware when I booted off the USB installer, so reverse
prime won't work and there will be no external monitor, which is a
completely new problem.
Public bug reported:
With my Legion Slim 7 in hybrid graphics mode (using amdgpu to drive the
laptop display) and an external monitor connected via the nvidia card on
a USB-C/HDMI connection, Xorg consistently uses around 40% CPU even with
no apps running.
If I put the laptop in discrete
/snd/controlC0: rocko 1978 F pulseaudio
/dev/snd/controlC1: rocko 1978 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 20 09:20:33 2021
InstallationDate: Installed on 2021-09-15 (5 days ago)
InstallationMedia: Ubuntu 21.10 "Impish
Public bug reported:
I installed Ubuntu 21.10 using ubiquity on a Legion Slim 7 with an amd
cpu/gpu using the amd gpu to drive the laptop screen but also an nvidia
graphics card. The installer ran fine but the installed image failed to
boot, just showing a blank screen. The installer had
Just to confirm, Ubuntu's mainline 5.14.5 kernel does boot successfully
on my machine with CONFIG_UBSAN_TRAP not set.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X /
I also can't boot the mainline 5.14-4 or 5.14-5 kernels on a Lenovo S7
(AMD 5800H and NVIDIA GPU) - it goes to a blank screen when trying to
boot graphics and freezes - I can't open a tty and have to hard reset
the system.
It looks like I have the laptop in the same mode as the other posters,
ie
Could this be the problem described here:
https://forums.developer.nvidia.com/t/ryzen-7-gtx-1660ti-blank-screen-
on-external-outputs-in-hybrid-graphics-mode/157800
ie (and this is the case if the external display is connected to the
NVIDIA card):
"Using amdgpu as a display offload source is
** 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
It has been a known issue for a while:
https://github.com/DisplayLink/evdi/issues/249
The trouble is we can patch and build it against 5.11 and it works at
first, but it freezes the system if you rearrange the layout, change the
resolution, unplug the screen, etc.
** Bug watch added:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917926
Title:
Window
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
Public bug reported:
This is https://github.com/BestImageViewer/geeqie/issues/539. It is
fixed in git now but is still present in the current version of geeqie
shipped with Ubuntu 21.04.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: geeqie 1:1.6-6
ProcVersionSignature: Ubuntu
*** 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
Actually, I don't think this bug was ever fixed. IIRC we suggested
putting in a configurable time for checking the SMART mon status but the
gnome dev said that the bug was due to buggy hard drive firmware and so
he wasn't going to do anything about it. It's a pain because each time
udisks2 is
systemd 246.6-1ubuntu1 and apport 2.20.11-0ubuntu48 fix this issue for
me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891657
Title:
systemd 100% cpu usage apport-autoreport.service: Failed with
I'm still seeing this bug with apport 2.20.11-0ubuntu48 and systemd
246.5-1ubuntu1. Do we need systemd 246.6 before it is fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891657
Title:
systemd
I changed
[Path]
PathChangedGlob=/var/crash/*.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891657
Title:
systemd 100% cpu usage apport-autoreport.service: Failed with result
Also, if you want to reduce the massive size of the journal logs that
this bug creates, do something like this:
sudo journalctl --rotate
sudo journalctl --vacuum-size=100M
That second command reduces it to 100 MB, but you can specify larger or
smaller sizes.
--
You received this bug
Trying again... After reading the linked systemd bug report, I changed
/usr/lib/systemd/system/apport-autoreport.path from having
PathExistsGlob to PathChangedGlob and ran sudo systemctl daemon-reload,
and this seemed to fix the problem:
[Unit]
Description=Process error reports when automatic
Doesn't systemd normally stop trying to start a service if it fails too
often? That's clearly not happening here, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891657
Title:
systemd 100%
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894031
Title:
Ubuntu
I ran into this and applied the workaround of deleting all the files in
/var/crash to stop the journalctl spam and 100% CPU usage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891657
Title:
However, the gnome-3-38 branch in dash-to-dock does work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880099
Title:
ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR:
Extension
I think this affects me, at least I no longer get dash-to-dock or
ubuntu-dock now that groovy has updated to 3.37.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880099
Title:
ubuntu-dock no longer
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893579
Title:
Ctrl + Alt + T
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893579
Title:
Ctrl + Alt + T and Fn keys not working
To manage
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
Bugs, which is subscribed to
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
Bugs, which is subscribed to
@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
Bugs, which is subscribed to Ubuntu.
** 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
Bugs, which is subscribed to 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
Bugs, which is subscribed to 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
Is this the same as
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889509
Title:
grub boot error : "symbol 'grub_calloc' not found
To
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
mutter:ERROR:../src/core/window.c:4841:set_workspace_state:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
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
Bugs, which is subscribed to 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
Bugs, which is subscribed to 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
Bugs, which is
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
Bugs, which is subscribed to 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866368
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868896
Title:
Minimized windows reappear when closing the overview
To manage
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
Bugs, which is subscribed to 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
Bugs, which is subscribed to
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
@Carlo:
> This premise seems incorrect to me. Gnome-tweaks variant switch worked
for gtk applications only, not for shell theme.
But that is actually how it used to work. The gnome-shell popups (such
as when you press Alt-F2) were indeed light, but the dropdown menus from
the top bar were dark.
: 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
Bugs, which is subscribed to Ubuntu.
I've not had a chance to test it recently - I haven't seen it happen for
a while, but I'm not switching between the nvidia and intel cards,
either, so I don't expect to. If I get a chance to try it on the weekend
I'll report back.
--
You received this bug notification because you are a member of
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
@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
Bugs, which is subscribed to 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842882
Title:
gnome-control-center no longer shows all the xrandr resolutions
To manage notifications about this
@Matthieu: Yes, nvidia on-demand works great in Ubuntu 19.10 with those
two variables. I also include this one (it's to make Vulkan only use the
nvidia card - Vulkan works really well for running DX 11 wine apps using
dxvk):
__VK_LAYER_NV_optimus=NVIDIA_only
--
You received this bug
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842882
Title:
gnome-control-center no longer shows all the
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842882
Title:
gnome-control-center no longer shows all
@Pete:
Yes, more recent kernels now can automatically power down the nvidia
card off when it's not in use, so you don't need bbswitch anymore.
What's even more cool is that with the nvidia 435.21 driver and the
version of X that comes with Ubuntu 19.10, you don't even need bumblebee
any more: if
It's fixed for me, too, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843520
Title:
ubuntu-dock right-click menu appears at the top-left corner of the
desktop (which in some cases is the
@seb128: Is the fix in the pull request at https://github.com/micheleg
/dash-to-dock/pull/975? That version of dash-to-dock works fine for me
in Eoan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unfortunately there isn't a working version of dash-to-dock for gnome
33/34, but dash-to-panel is a nice workaround for this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843520
Title:
This is probably the relevant error:
Sep 11 12:24:12 xps15 gnome-shell[16574]: JS ERROR: TypeError:
mutterWindow.get_texture(...).get_size is not a function
_cloneTexture@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/windowPreview.js:382:62
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842882
Title:
gnome-control-center no longer
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
Bugs, which is subscribed to Ubuntu.
Do you mean is it the same bug what I described in comment #10? My
comment #11 is more of a easy workaround to get the dark menus (you can
easily switch between dark and light with this, as well).
Regarding comment #10, I haven't confirmed the problem with the dark
user shell themes is a
> Maybe see https://github.com/ubuntu/yaru/issues/1483
Great, thanks for that link! So I got dark menus working by doing the
following:
* I cloned the source from https://github.com/ubuntu/yaru.git:
git clone https://github.com/ubuntu/yaru.git
* After changing into the yaru folder, I changed
Another issue with it is that if you do install a dark shell theme in
Eoan, the system menu often has unreadable text. An example is pop-dark
- see https://askubuntu.com/questions/1149991/dark-shell-theme-that-
fits-yaru-dark. I think the menus are supposed to look something like
this:
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!
--
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
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
1 - 100 of 2436 matches
Mail list logo
