Public bug reported:
The gnome-shell built-in screencast recorder doesn't currently
(43.0-1ubuntu2/lunar) record audio. According to this comment:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5524#note_1465711
enabling audio recording only requires changing a parameter via dbus. If
the
Public bug reported:
fonttools 4.34.4-1 causes an autopkgtest regression in glyphslib, see
log excerpt below and the linked Debian bug.
=== FAILURES ===
_ test_designspace_generation_regular_same_family_name[defcon]
aptly is Fix Release in Kinetic in:
aptly (1.4.0+ds1-7) unstable; urgency=medium
* Team upload.
* Add support for zstd compression (Closes: #1010465)
** Changed in: aptly (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Possibly related: the user graphical-session.target unit is never
reached in Jammy. From Impish and Jammy we have for `systemctl --user
is-active graphical-session.target`:
- Impish clean install: active
- Jammy clean install: inactive
Note that this means that the .service units under
** Tags added: rls-jj-incoming
--
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/1743366
Title:
The user session should run under systemd
To manage notifications about this
Interesting, thanks for verifying. I just re-tested this and indeed for
`systemctl --user is-active graphical-session.target` we have
- Impish clean install: active
- Jammy clean install: inactive
So looks like this we switched to systemd sessions at some point, but
this bug never got closed,
Maybe useful: https://wiki.gnome.org/Initiatives/SystemdUser
I'll add that I was confused by this as systemd.special(7) says about
graphical-session.target:
This target is active whenever any graphical session is running. [...]
and it took me a while to figure out that's not true in our case.
This bug was filed pre-Bionic and explicitly mentions Bionic, but looks
like the issue is still present in Jammy:
$ systemctl --user is-active graphical-session.target
inactive
verified in a clean Jammy install and also on Impish (thanks ~ogayot).
Other than the .path units under
This is fixed in 1.12.1-1ubuntu1:
* debian/conrol:
- switch to fuse3
* debian/patches/gitlab-use-fuse3.patch:
- cherry pick the PR from Trevinho to use fuse3 since it was reviewed
by James and wanted for the LTS
** Changed in: xdg-desktop-portal (Ubuntu)
Status: In
Good catch, I filed a separate bug for ntfs-3g:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1957756
and mentioned it in the MIR bug LP: #1934510.
** No longer affects: ntfs-3g (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Also affects: ntfs-3g (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1956949
Title:
CPC AWS jammy builds fail with: "fuse3 :
@Bernd "not being seeded" means that unionfs-fuse isn't in the set of
packages that define what goes into the Ubuntu 'main' component. In
summary this is done by choosing some "seed" packages and computing
their (build-)dependency tree, see [1,2] if you want to know more.
Automatic syncing of
Hi Tobias and thanks for this bug report. Shortcut clashes are
unavoidable, but I believe terminal emulators should do their best to
avoid taking over the F keys. I was going to suggest you to disable
the shortcut from the gnome-terminal settings, but apparently the
shortcut is not listed there
In gnome-terminal 3.36.2-1ubuntu1 (Groovy) the F10 selects (without
"clicking") the New Tab button, for which a keyboard shortcut already
exists. The shortcut can't be disabled from the gnome-terminal settings,
not even disabling all the shortcuts by unchecking the "Enable
shortcuts" checkbox.
I
Not a fix but a workaround:
I installed the gnome-shell-extension-bluetooth-quick-connect package.
In integrates well with the Gnome UI, adding a menu similar to the WiFi
networks one but for Bluetooth devices, and it connects almost every
time.
--
You received this bug notification because you
This bug has been fixed in version 31-1 of the package, now in Focal as
a Debian sync, so I'm marking it a Fix Released.
** Changed in: gnome-shell-extension-dash-to-panel (Ubuntu Focal)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of
** 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
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
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.
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
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
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"
Public bug reported:
Steps to reproduce:
1. On a laptop, connect an external monitor and set it up as the "primary
display" in a "Join Displays" setup.
2. Setup a few workspaces in the primary display by placing windows in them,
e.g. a few terminals.
3. Disconnect the external monitor. The
Copy/paste fail, I meant gnome-shell 3.36.0-2ubuntu1.
--
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/1868990
Title:
Various actions produce images of applications running on all
I'm hitting this too with the last upgrade that brought in gnome-shell
3.4.1-0ubuntu2. Happens both in Xorg and Wayland sessions.
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I can confirm this happens on both a Thinkpad T480s and X250. Acting on
the sliders does work, they change the volume/brightness, but they're
not updated to show the current setting.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Bug still present in the current devel version of Focal Fossa.
--
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/1753070
Title:
Cannot restore default alert sound
Maintainer of the fonts-hack Debian package here. I can't reproduce the
issue with fonts-hack 3.003-3 on Eoan, I get the expected result, i.e.:
* Two grapheme clusters are displayed: Latin small letter a with acute
accent, Latin small letter e.
On which Ubuntu release are you observing it?
**
** Also affects: gnome-control-center (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: gnome-control-center (Ubuntu Eoan)
Importance: Low
Status: Confirmed
** Also affects: gnome-control-center (Ubuntu Bionic)
Importance: Undecided
Status: New
**
This is still an issue in Disco, with a difference: there is no
"default" button anymore in the Sound settings, only
Bark|Drip|Glass|Sonar, none of which is the original Ubuntu bell from
the Yaru theme.
Setting it to "Bark" is a good way to remember this has to be fixed :)
--
You received this
** Changed in: zsh (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Title:
demotion of pcre3 (8.x) a.k.a pcre (without the 3)
Just found
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/1
which addresses exactly this issue.
--
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.
Public bug reported:
On a clean Disco install by default we get the desktop icons, but the
extension appears as disabled in gnome-tweaks: the setting is not
consistent with the actual observed behavior.
It seems that the extension "switch" in gnome-tweaks has no effect: even
when turned off
35 matches
Mail list logo
