Also noticed in Ubuntu 23.10 in every boot:
nov 22 04:10:54 fpgrpi gnome-shell[2402]: JS ERROR: Gio.IOErrorEnum:
GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
For those who prefer run/test gdm3 in Wayland the Ubuntu's patch that
disables it does this:
Original 61-gdm.rules file lines:
# For nvidia drivers versions Above 510, keep Wayland by default
ATTR{version}=="[5-9][1-9][0-9].*", GOTO="gdm_end"
Patched lines:
# For nvidia drivers versions Above
Didn't realize that. I'll wait for final release.
--
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/2012309
Title:
gdm3: autostart folder for .desktop files is not working in Ubuntu
> Seems like I had the bug yesterday but it's fixed today?
Same here. It doesn't work but just worked after installing these
updates:
libadwaita-1-0:arm64 (1.3.1-1ubuntu1)
gir1.2-adw-1:arm64 (1.3.1-1ubuntu1)
mutter-common:arm64 (44.0-1ubuntu1)
mutter-common-bin:arm64 (44.0-1ubuntu1)
> Because, per the documentation, the method changed. Therefore, this was an
> upstream change. Therefore, it is your *opinion* that it should have stayed
> the same. That's not a bug or regression. In programming and methodology,
> things change all the time and the downstreams must adapt to
apport information
** Attachment added: "modified.conffile..etc.pam.d.gdm-password.txt"
https://bugs.launchpad.net/bugs/2012311/+attachment/5656117/+files/modified.conffile..etc.pam.d.gdm-password.txt
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
--
You received this bug
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2012311/+attachment/5656115/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
apport information
** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt"
https://bugs.launchpad.net/bugs/2012311/+attachment/5656116/+files/modified.conffile..etc.gdm3.custom.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2012311/+attachment/5656114/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
apport information
** Tags added: apport-collected lunar
** Description changed:
Problem summary:
After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the
options to Restart and Shutdown the system are not working anymore.
In Ubuntu 22.10 when you
I don't understand why this bug was marked as Opinion. If something
works in the previous version and don't work in current version is a Bug
or a Regression.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Public bug reported:
Problem summary:
After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the
options to Restart and Shutdown the system are not working anymore.
In Ubuntu 22.10 when you are in the gdm3 login screen and choose Restart
or Shutdown it presents
Public bug reported:
Problem summary:
After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) gdm3
doesn't autostart the applications (.desktop files) placed in the folder
/usr/share/gdm/greeter/autostart/
Notice that gdm3 documentation states that the official
** Package changed: gnome-shell (Ubuntu) => yaru-theme (Ubuntu)
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "Ubuntu 22.10 OK"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012282/+attachment/5655904/+files/Ubuntu_22_10_OK.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "Ubuntu 23.04 BAD"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012282/+attachment/5655905/+files/Ubuntu_23_04_BAD.png
--
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:
Problem summary:
After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the
gnome-shell application folders background is shown in white color instead of
dark grey color making impossible to read it's contents. I'm using the default
Ubuntu
I can't understand some decisions. IMHO this is by far the worse
downgrade that a remote application can have.
--
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/1987159
Public bug reported:
There are some options missing in the arm64 built compared to the same
amd64 build: the arm64 build misses the rightmost icon that includes the
"Extensions", "About" and "Exit" options.
Here are both screenshots from amd64 and arm64 builds, same gnome-todo
version
Proposed fix tested in hirsute on a Raspberry Pi4 arm64 and on an PC
amd64.
Packages installed from hirsute-proposed:
libgjs0g (1.68.1-1~ubuntu0.21.04.1)
gjs (1.68.1-1~ubuntu0.21.04.1)
And, after reboot, do those tests:
1./ Test case:
gjs -c
Proposed fix tested in hirsute on a Raspberry Pi4 arm64, kernel
5.11.0-1009-raspi
Packages installed from hirsute-proposed:
gnome-shell (3.38.4-1ubuntu3~21.04.1)
gnome-shell-common (3.38.4-1ubuntu3~21.04.1)
gnome-shell-extension-prefs (3.38.4-1ubuntu3~21.04.1)
After reboot I've activated
Finally will the fix be released for Hirsute? Seems that it has been
moved form Hirsute (Proposed) to Impish.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs
Forget about the messages that I show in the previous post: it seems
that this problem is also happening in Ubuntu 20.10 groovy and are
unrelated to the original bug. I didn't realize these messages before
because in groovy these messages are way less informative than in
hirsute. In groovy it only
fprietog-VirtualBox gnome-shell[1339]: value "nan" of type
'gfloat' is invalid or out of range for property 'x' of type 'gfloat'
abr 23 02:54:52 fprietog-VirtualBox gnome-shell[1339]: value "nan" of type
'gfloat' is invalid or out of range for property 'y' of type 'gfl
Just tested amd64 packages with the same results than arm64: problem is
solved.
Thanks and best regards.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on
Hello Brian,
Just tested arm64 build; updated these packages:
- gjs_1.67.2-2ubuntu2_arm64.deb
fprietog@fpgrpi:~$ apt-cache policy gjs
gjs:
Instalados: 1.67.2-2ubuntu2
Candidato: 1.67.2-2ubuntu2
Tabla de versión:
*** 1.67.2-2ubuntu2 100
100 /var/lib/dpkg/status
1.67.2
and not related
to indicators:
abr 21 19:25:19 fprietog-VirtualBox gnome-shell[1361]: JS ERROR: TypeError:
method Gio.File.delete_async: At least 3 arguments required, but only 2 passed
_handleLockScreenWarning@resource:///org/gnome/shell/ui/main.js:323:24
_initializeUI/<@resource:///org/gnome/sh
Public bug reported:
Problem tested in two different environments:
- Ubuntu 21.04 Beta amd64
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)
After upgrading these packages:
libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin 2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1
The app
And the 2nd point is also an "user" problem.
When we use the dconf-editor GUI we are changing the dconf keys for the
user that executes the command, usually your personal user. So changing
it from there has no effect because the user that launches the greeter
is different; 'gdm'.
So the solution
BTW: as Joris Le Blansch wrote, using dconf-editor GUI to set /org/gnome
/login-screen/disable-user-list to ON has no effect and after reboot
userlist is shown as before.
So, at this point:
1. Manually changing the file '/etc/gdm3/greeter.dconf-defaults' uncommenting
the lines:
I managed to get some journalctl entries related with the gdm starting
error:
abr 09 20:54:01 testuser-VirtualBox generate-config[699]: warning: Failed to
read keyfile '/usr/share/gdm/dconf/90-debian-settings': Key file does not start
with a group
abr 09 20:54:01 testuser-VirtualBox systemd[1]:
Public bug reported:
Ubuntu 17.10 final
gdm3 package version is 3.26.1-3ubuntu2
Problem details:
The file /etc/gdm3/greeter.dconf-defaults got this option commented by default:
# disable-user-list=true
I've used this option with Ubuntu 17.04 (GNOME session) in order to not
Amr Ibrahim (amribrahim1987) wrote on 2015-08-26:
Is this related?
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1040158
---
It's related but not the same. The report you pointed seems to be quite
old and states that nautilus takes focus only
IMHO this is an important bug; well, it doesn't break any important OS
feature but it affects the general image of Unity Ubuntu the users
should have because it happens with a usually frequent task execution.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
34 matches
Mail list logo
