Public bug reported:
I'm using Ubuntu 20.10 groovy (beta).
The Gnome calendar is not syncing with Google calendar online account.
In Ubuntu 20.04 (focal) there is no such problem.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-calendar 3.38.0-1
ProcVersionSignature: Ubuntu
In Ubuntu 20.04 there is no such problem: all title bars have the same
thickness.
--
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/1898324
Title:
[groovy] Different thickness
Public bug reported:
I'm using Ubuntu 20.10 (beta).
The title bar thickness is different between gtk3 / gtk2 applications.
Gtk3 applications have a thicker title bar. I think all thickness must
be the same to keep the visual identity of the OS.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
[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 mutter in Ubuntu.
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Sure
The Keyboard Shortcuts for Lock Screen is set to Ctrl+Alt+L
Found in Settings -> Keyboard Shortcuts -> Lock screen -> Ctrl+Alt+L
1) I can't lock the screen using the (keybinding / shortcut) Ctrl+Alt+L
https://i.imgur.com/VKiXvZV.png
2) I can lock the screen by clicking on the lock option
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
This bug recurred with the last two 20.04 Updater packages, starting
mid-September. The initramfs upacking bug 1835660 recurred about the
same time. Turning off the Ubuntu splash screen seems to avoid the
problem, but when it doesn't (or until you realize that you have to make
that change); the
Could you add your 'journalctl -b 0' log after getting the issue? can
you manually lock the screen from the indicator or using the keybinding?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
I'm from an upgraded ubuntu 20.04 notebook that freezes less than 1
minute after login. The only time it unfrozen a bit it thrown the popup
with this error. Well, at least there was the link to this bug as
duplicate or something.
The solution they suggested here
(In reply to Nate Graham from comment #41)
>
> Even if there's no explicit Qt support (is this still true?) we could still
> implement it ourselves on the KDE side.
I should note that Qt support is explicitly "good" for X11, and Wayland seems
ready for up to 16 buttons. The reasons why I
(In reply to Nate Graham from comment #41)
> Re-opening since this is a reasonable request. Binding shortcuts/actions to
> additional mouse buttons seems reasonable.
>
> Even if there's no explicit Qt support (is this still true?) we could still
> implement it ourselves on the KDE side.
I'm not
(removed myself as assignee)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/62949
Title:
No way to configure mouse button number
To manage notifications about this bug
The problem is with Pithos 1.5 which I recently installed. It has two
optional setting. One looks like it disables the screen saver (screen
blanking) and the other is not to pause in screen saver mode (my problem
os loosing audio).
--
You received this bug notification because you are a member
Also does not work for me on Ubuntu 20.10 when running on Xorg.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1848277
Title:
Won't start, get "cannot open display: :0"
1. The specific steps or actions you took that caused you to encounter
the problem.
-I tried to set the screen to lock at a specific interval and it doesn't lock
Settings-> Privacy-> Screen Lock -> Automatic Screen Lock -> Enabled
Settings-> Privacy-> Screen Lock -> Automatic Screen Lock -> 30
Should be:
Settings-> Privacy-> Screen Lock -> Automatic Screen Lock Delay -> 30 seconds
--
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/1898153
Title:
I upgraded
The description isn't clear, it doesn't lock at the same time than what?
Also what has the filemanager having to do with the issue?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
** Changed in: gnome-shell (Fedora)
Status: Unknown => Won't Fix
** Changed in: gnome-shell (Fedora)
Importance: Unknown => Undecided
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
The options for locking, blanking and shortcut keys are in the gnome-
control-center
** Package changed: ubuntu => gnome-control-center (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
You have been subscribed to a public bug:
I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go
blank at the set time. I think this issue also effects the shortcuts
not working also.
I'm using nemo as my file manager I followed these instructions below
The audio feed from the io ports is indeed going to a stand alone
bluetooth transmitter located central in the house. I did split off the
audio cable to feed a stereo located next to the desktop. The stereo
also looses the audio feed when the screen blanks.
--
You received this bug
the bud id of the associated crash 1898090
--
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/1897959
Title:
Audio Shuts Down with Screen Blanking
To manage notifications about
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.
Ubuntu version : 20.04
How to trigger :
1) Lauch nautilus
2) Type CTRL-L
3) Type ftp://
4) The dialog opens and asks for an anonymous connection or a username and a
password.
5) Type an username and password
6) Nautilus is stuck trying to load the directory.
The FTP I'm trying to connect to is
** This bug is no longer a duplicate of bug 1897765
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw() from
WindowManager::_sizeChangedWindow
** Bug watch added: Red Hat Bugzilla #1402492
** Summary changed:
- gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting")
from meta_window_actor_thaw()
+ gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting")
from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
** Package
Timo,
Can you test this?
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1453.patch
--
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/1897765
Title:
gnome-shell crashed
The relevant log lines are:
[ 2021.323087] bryant gnome-shell[6061]: JS ERROR: TypeError:
actor.__animationInfo is undefined
_sizeChangedWindow@resource:///org/gnome/shell/ui/windowManager.js:1385:9
[ 2021.349267] bryant gnome-shell[6061]: Error in
Still happening on Ubuntu 18.04, but in Ubuntu 20.04, gnome-terminal now
has an option to keep or not the working directory.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
31 matches
Mail list logo
