[Desktop-packages] [Bug 2061211] Re: Invalid escape sequences in regexes when installing gedit
It can also be reproduced reinstalling gedit (in this example in aarch64
architecture):
# apt install --reinstall gedit
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias... Hecho
Leyendo la información de estado... Hecho
0 actualizados, 0 nuevos se instalarán, 1 reinstalados, 0 para eliminar y 0 no
actualizados.
Se necesita descargar 353 kB de archivos.
Se utilizarán 0 B de espacio de disco adicional después de esta operación.
Des:1 http://ports.ubuntu.com/ubuntu-ports noble/universe arm64 gedit arm64
46.2-2 [353 kB]
Descargados 353 kB en 0s (1.178 kB/s)
(Leyendo la base de datos ... 221724 ficheros o directorios instalados
actualmente.)
Preparando para desempaquetar .../gedit_46.2-2_arm64.deb ...
Desempaquetando gedit (46.2-2) sobre (46.2-2) ...
Configurando gedit (46.2-2) ...
/usr/lib/aarch64-linux-gnu/gedit/plugins/externaltools/library.py:212:
SyntaxWarning: invalid escape sequence '\-'
RE_KEY = re.compile('^([a-zA-Z_][a-zA-Z0-9_.\-]*)(\[([a-zA-Z_@]+)\])?$')
/usr/lib/aarch64-linux-gnu/gedit/plugins/snippets/substitutionparser.py:162:
SyntaxWarning: invalid escape sequence '\s'
match = re.match('?%s\s*' % self.REG_GROUP, tokens)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/2061211
Title:
Invalid escape sequences in regexes when installing gedit
Status in gedit package in Ubuntu:
Confirmed
Bug description:
On a clean install of the 24.04 beta, if you do a "sudo apt install
gedit", you get the following messages at the end of the install:
/usr/lib/x86_64-linux-gnu/gedit/plugins/externaltools/library.py:212:
SyntaxWarning: invalid escape sequence '\-'
RE_KEY = re.compile('^([a-zA-Z_][a-zA-Z0-9_.\-]*)(\[([a-zA-Z_@]+)\])?$')
/usr/lib/x86_64-linux-gnu/gedit/plugins/snippets/substitutionparser.py:162:
SyntaxWarning: invalid escape sequence '\s'
match = re.match('?%s\s*' % self.REG_GROUP, tokens)
So there are 2 issues with regexes.
Bug #2055010 reports the first of these, but not the second, and it
also reports a different issue as "the huger problem" (one that I
can't reproduce). I hope I'm making the right call in opening a new
bug report specifically for these regex issues.
Some more details:
- on the clean install, I did apply all available updates before trying to
install gedit
- you can also reproduce this issue from the live ("try ubuntu") environment
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gedit 46.2-1build1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.496
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 13 08:41:26 2024
LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2061211/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2029480] Re: SyntaxWarnings with Python3.12
I'm sorry but the related fix seem to be not complete: during upgrade
from 23.10.1 mantic to 24.04 noble it updates hplip-data
3.23.12+dfsg0-0ubuntu5 from previous 3.22.10+dfsg0-2ubuntu1 and it
doesn't generate SyntaxWarnings... but a few moments later, then during
python3 (3.12.3-0ubuntu1) configuration:
Configurando python3 (3.12.3-0ubuntu1) ...
running python rtupdate hooks for python3.12...
...
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape sequence
'\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape sequence
'\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape sequence
'\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/fax/ledmfax.py:46: SyntaxWarning: invalid escape sequence '\d'
http_result_pat = re.compile(b"""HTTP/\d.\d\s(\d+)""", re.I)
...
running python post-rtupdate hooks for python3.12...
You can also reinstall hplip-data using apt and ending in the same
problem:
# apt install --reinstall hplip-data
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias... Hecho
Leyendo la información de estado... Hecho
0 actualizados, 0 nuevos se instalarán, 1 reinstalados, 0 para eliminar y 0 no
actualizados.
Se necesita descargar 6.467 kB de archivos.
Se utilizarán 0 B de espacio de disco adicional después de esta operación.
Des:1 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 hplip-data all
3.23.12+dfsg0-0ubuntu5 [6.467 kB]
Descargados 6.467 kB en 1s (8.035 kB/s)
(Leyendo la base de datos ... 221724 ficheros o directorios instalados
actualmente.)
Preparando para desempaquetar .../hplip-data_3.23.12+dfsg0-0ubuntu5_all.deb ...
Desempaquetando hplip-data (3.23.12+dfsg0-0ubuntu5) sobre
(3.23.12+dfsg0-0ubuntu5) ...
Configurando hplip-data (3.23.12+dfsg0-0ubuntu5) ...
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape sequence
'\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape sequence
'\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape sequence
'\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/fax/ledmfax.py:46: SyntaxWarning: invalid escape sequence '\d'
http_result_pat = re.compile(b"""HTTP/\d.\d\s(\d+)""", re.I)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/2029480
Title:
SyntaxWarnings with Python3.12
Status in HPLIP:
Confirmed
Status in hplip package in Ubuntu:
Fix Released
Bug description:
Fedora 39 uses Python 3.12 by default, which generates many
SyntaxWarnings when running hplip scripts.
Most warnings are due regular expressions in strings, so making them
raw fixes the issue.
The patch is attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/2029480/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991901] Re: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
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 asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 @resource:///org/gnome/shell/ui/init.js:21:20 ... nov 22 04:10:59 fpgrpi gnome-shell[2402]: JS ERROR: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 @resource:///org/gnome/shell/ui/init.js:21:20 nov 22 04:11:04 fpgrpi gdm-password][8229]: gkr-pam: unable to locate daemon control file nov 22 04:11:04 fpgrpi gnome-shell[2402]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: Set global engine failed: Se canceló la operación _promisify/proto[asyncFunc]/ @resource:///org/gnome/shell/ui/init.js:21:20 ### Promise created here: ### _setEngine@resource:///org/gnome/shell/misc/ibusManager.js:303:30 setEngine@resource:///org/gnome/shell/misc/ibusManager.js:326:24 activateInputSource@resource:///org/gnome/shell/ui/status/keyboard.js:499:31 _callHandlers@resource:///org/gnome/gjs/modules/core/_signals.js:130:42 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:119:10 activate@resource:///org/gnome/shell/ui/status/keyboard.js:68:14 _inputSourcesChanged@resource:///org/gnome/shell/ui/status/keyboard.js:633:33 reload@resource:///org/gnome/shell/ui/status/keyboard.js:373:14 _ibusSetContentType@resource:///org/gnome/shell/ui/status/keyboard.js:708:14 _callHandlers@resource:///org/gnome/gjs/modules/core/_signals.js:130:42 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:119:10 _setContentType@resource:///org/gnome/shell/misc/ibusManager.js:278:14 @resource:///org/gnome/shell/ui/init.js:21:20 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1991901 Title: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available Status in gnome-shell package in Ubuntu: Confirmed Bug description: This error is too noisy and also not an error. Many systems and most desktops won't have fingerprint devices. JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042866] [NEW] Warning: Permissions for /etc/netplan/01-use-network-manager.yaml are too open. Netplan configuration should NOT be accessible by others.
Public bug reported: This warning is shown in the system journal (during boot): nov 06 17:15:23 fpgrpi generate[840]: Permissions for /etc/netplan/01-use-network-manager.yaml are too open. Netplan configuration should NOT be accessible by others. The file /etc/netplan/01-use-network-manager.yaml came from the package ubuntu-raspi-settings-desktop and its post install permissions are -rw-r --r-- (group and others readable). A simple workaround is to remove the file read permission for group and others, as suggested, using this command: sudo chmod 600 /etc/netplan/01-use-network-manager.yaml Additional info: OS: Ubuntu 23.10 aarch64 (Mantic) Host: Raspberry Pi 4 Model B Rev 1.4 Kernel: 6.5.0-1006-raspi # lsb_release -r No LSB modules are available. Release:23.10 # apt-cache policy ubuntu-raspi-settings-desktop ubuntu-raspi-settings-desktop: Instalados: 23.10.6 Candidato: 23.10.6 Tabla de versión: *** 23.10.6 500 500 http://ports.ubuntu.com/ubuntu-ports mantic/main arm64 Packages 100 /var/lib/dpkg/status ** Affects: ubuntu-raspi-settings (Ubuntu) Importance: Undecided Status: New ** Package changed: ubuntu-settings (Ubuntu) => ubuntu-raspi-settings (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2042866 Title: Warning: Permissions for /etc/netplan/01-use-network-manager.yaml are too open. Netplan configuration should NOT be accessible by others. Status in ubuntu-raspi-settings package in Ubuntu: New Bug description: This warning is shown in the system journal (during boot): nov 06 17:15:23 fpgrpi generate[840]: Permissions for /etc/netplan/01-use-network-manager.yaml are too open. Netplan configuration should NOT be accessible by others. The file /etc/netplan/01-use-network-manager.yaml came from the package ubuntu-raspi-settings-desktop and its post install permissions are -rw-r--r-- (group and others readable). A simple workaround is to remove the file read permission for group and others, as suggested, using this command: sudo chmod 600 /etc/netplan/01-use-network-manager.yaml Additional info: OS: Ubuntu 23.10 aarch64 (Mantic) Host: Raspberry Pi 4 Model B Rev 1.4 Kernel: 6.5.0-1006-raspi # lsb_release -r No LSB modules are available. Release: 23.10 # apt-cache policy ubuntu-raspi-settings-desktop ubuntu-raspi-settings-desktop: Instalados: 23.10.6 Candidato: 23.10.6 Tabla de versión: *** 23.10.6 500 500 http://ports.ubuntu.com/ubuntu-ports mantic/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2042866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012311] Re: gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04
> 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) libmutter-12-0:arm64 (44.0-1ubuntu1) gir1.2-mutter-12:arm64 (44.0-1ubuntu1) gnome-control-center:arm64 (1:44.0-1ubuntu1) gnome-control-center-data:arm64 (1:44.0-1ubuntu1) gnome-control-center-faces:arm64 (1:44.0-1ubuntu1) I've checked the changelog of these updates without finding the concrete one that fixed the problem. But it's fixed... so we're happy :D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012311 Title: gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04 Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: 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 a dialog box saying that the action will be auto performed in 60 seconds, with two buttons, one to cancel and another to perform the action at once. In Ubuntu 23.04 choosing Restart or Shutdown does nothing at all... Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gdm3 gdm3: Instalados: 43.0-3ubuntu2 Candidato: 43.0-3ubuntu2 Tabla de versión: *** 43.0-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 Package: gdm3 43.0-3ubuntu2 PackageArchitecture: arm64 ProcVersionSignature: Ubuntu 5.19.0-1015.22-raspi 5.19.17 Tags: lunar Uname: Linux 5.19.0-1015-raspi aarch64 UpgradeStatus: Upgraded to lunar on 2023-03-20 (0 days ago) UserGroups: N/A _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-05-04T11:33:42 mtime.conffile..etc.gdm3.custom.conf: 2023-03-07T19:16:26 mtime.conffile..etc.pam.d.gdm-password: 2022-05-08T18:01:33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012311] [NEW] gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04
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 a dialog box saying that the action will be auto performed in 60 seconds, with two buttons, one to cancel and another to perform the action at once. In Ubuntu 23.04 choosing Restart or Shutdown does nothing at all... Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gdm3 gdm3: Instalados: 43.0-3ubuntu2 Candidato: 43.0-3ubuntu2 Tabla de versión: *** 43.0-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2012311 Title: gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04 Status in gdm3 package in Ubuntu: New Bug description: 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 a dialog box saying that the action will be auto performed in 60 seconds, with two buttons, one to cancel and another to perform the action at once. In Ubuntu 23.04 choosing Restart or Shutdown does nothing at all... Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gdm3 gdm3: Instalados: 43.0-3ubuntu2 Candidato: 43.0-3ubuntu2 Tabla de versión: *** 43.0-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012309] [NEW] gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04
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 autostart folder is /usr/share/gdm/autostart/LoginWindow/ but placing desktop files in this folder never worked for me in any Ubuntu release. However, placing desktop files in the folder /usr/share/gdm/greeter/autostart/ worked in Ubuntu 22.10 and previous releases, but it's broken in Ubuntu 23.04. So it may be correct that /usr/share/gdm/greeter/autostart/ don't work anymore as the documented folder is /usr/share/gdm/autostart/LoginWindow/ ... but that one didn't work either. There are several packages that rely in the correct working of these autostart folders. E.g. the package spice-vdagent creates these two .desktop files: /usr/share/gdm/autostart/LoginWindow/spice-vdagent.desktop /usr/share/gdm/greeter/autostart/spice-vdagent.desktop One in each autostart folder... just in case. But none of these works in Ubuntu 23.04. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gdm3 gdm3: Instalados: 43.0-3ubuntu2 Candidato: 43.0-3ubuntu2 Tabla de versión: *** 43.0-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, 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 23.04 Status in gdm3 package in Ubuntu: New Bug description: 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 autostart folder is /usr/share/gdm/autostart/LoginWindow/ but placing desktop files in this folder never worked for me in any Ubuntu release. However, placing desktop files in the folder /usr/share/gdm/greeter/autostart/ worked in Ubuntu 22.10 and previous releases, but it's broken in Ubuntu 23.04. So it may be correct that /usr/share/gdm/greeter/autostart/ don't work anymore as the documented folder is /usr/share/gdm/autostart/LoginWindow/ ... but that one didn't work either. There are several packages that rely in the correct working of these autostart folders. E.g. the package spice-vdagent creates these two .desktop files: /usr/share/gdm/autostart/LoginWindow/spice-vdagent.desktop /usr/share/gdm/greeter/autostart/spice-vdagent.desktop One in each autostart folder... just in case. But none of these works in Ubuntu 23.04. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gdm3 gdm3: Instalados: 43.0-3ubuntu2 Candidato: 43.0-3ubuntu2 Tabla de versión: *** 43.0-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012309/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012282] Re: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders
** 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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012282 Title: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders Status in gnome-shell package in Ubuntu: New Status in yaru-theme package in Ubuntu: New Bug description: 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 theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012282] Re: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders
** 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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012282 Title: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders Status in gnome-shell package in Ubuntu: New Bug description: 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 theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012282] Re: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders
** 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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012282 Title: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders Status in gnome-shell package in Ubuntu: New Bug description: 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 theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012282] [NEW] [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders
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 theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012282 Title: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders Status in gnome-shell package in Ubuntu: New Bug description: 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 theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
As a temporary workaround I've installed packages "transmission- common_4.0.1-1" and "transmission-gtk_4.0.1-1" from Debian sid (unstable) and both works flawlessly in Ubuntu 22.10 so this bug is gone using these packages. I hope these packages will be picked for Ubuntu 23.04 publish. Note: the Debian package "transmission-gtk_4.0.1-1" have a broken dependence in Ubuntu 22.10. It requires "libevent-2.1-7 (>= 2.1.8-stable)" but in Ubuntu 22.10 the package is named "libevent-2.1-7a". It's not a problem because "transmission-gtk_4.0.1-1" is installed marked as a broken package, but it works flawlessly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
There is a new transmission version available. Hope it reach Ubuntu repo soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
@Zakhar Don't waste your time with this application. In kinetic the VNC support has been dropped because GNOME rules, and Ubuntu, as a GNOME sub-brand, blindly followed that decission. You can still use another VNC server if you are using X11 (I don't know a VNC server that works for Wayland). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop... abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop. abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libcuda.so.1 abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libnvidia-encode.so.1 abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started On X11: --- abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions vanished abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 19. abr 25 00:12:18 fpgrpi systemd[2859]: Stopped GNOME Remote Desktop. abr 25 00:12:18 fpgrpi systemd[2859]: Starting GNOME Remote Desktop... abr 25 00:12:18 fpgrpi systemd[2859]: Started GNOME Remote Desktop. abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load libcuda.so.1 abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load libnvidia-encode.so.1 abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: RDP server started abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: VNC server started To manage
[Desktop-packages] [Bug 1987159] Re: Drop VNC support from GNOME Remote Desktop in Kinetic
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 Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987159 Title: Drop VNC support from GNOME Remote Desktop in Kinetic Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: RDP has significantly improved privacy and performance compared to VNC. I am struggling to find any use cases where GNOME's VNC should be preferred to RDP. GNOME is so far unwilling to provide full VNC options in the GNOME Settings app. The VNC feature was labeled as Legacy in Ubuntu 22.04 LTS. There is value in only providing a single remote desktop method by default that works well. gnome-remote-desktop 43 by default only builds the RDP provider and so far I haven't seen complaints about that. Therefore, I think we should drop the VNC feature for Ubuntu 22.10. Otherwise, we need to: 1. enable VNC in gnome-remote-desktop 43 2. Update the VNC patch in gnome-control-center 43 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
Unfortunately I'm still having this problem. Just tested in Ubuntu 22.04 amd64 and arm64. No updates or phased updates pending... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
valgrind.log file attached. ** Attachment added: "valgrind.log" https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+attachment/5597936/+files/valgrind.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
The proposed packages didn't solve the problem... Seems to but after a reboot it starts to fail again. Please test the problem in Ubuntu as asked in the previous post. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
Why are you using xubuntu? I just use distrotest.net with xubuntu 22.04 and Ubuntu 22.04. - in xubuntu it works without error (attached screenshot). - in Ubuntu (GNOME) it fails. But problem was reported in Ubuntu (GNOME) from the beginning. Please, use Ubuntu (GNOME) instead of xubuntu and it will fail for sure. ** Attachment added: "It works in xubuntu..." https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+attachment/5597913/+files/Captura%20desde%202022-06-17%2011-20-11.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
I'm using locale es_ES but I just tested with locale en_US and fails as well. The UI used is transmission-gtk. Steps to reproduce the problem: - Open transmission-gtk. - Open a terminal and enter journalctl -f to see the errors that will be generated. - Open a torrent file. - Open the torrent Properties and check it's tabs. All seems to be correct... - Close properties. At this moment there will be lots of gtk errors shown in the terminal. - Open the torrent Properties again and check it's tabs: the info is scrambled across tabs. I've attached a video showing the problem. ** Attachment added: "Video showing the problem" https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+attachment/5597806/+files/Screencast%20from%2016-06-22%2021%3A44%3A55.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
The problem happens with all torrents. You can use this one: https://releases.ubuntu.com/22.04/ubuntu-22.04-desktop-amd64.iso.torrent -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
@waveform I think that the meaning of "basic" feature in an OS is something that can't be stated universally because it depends of the usage done by each set of users. In my opinion remote desktop is a "basic" feature because I use the Raspberry Pi remotely. And for a Raspberry Pi that's nothing unusual at all. I don't know what you mean when said that remote desktop is a recent addition to the desktop... gnome-remote-desktop is a recent software and also Raspberry Pi Desktop official support, but I've using Ubuntu's default remote desktop for years: vino-server (in fact, I'm still using to connect to the greeter). I agree with you that testing remote desktop before release is a good idea. You may think that it's not a "basic" feature as it can be sorted using other software, but it creates a problem for the users (we're lazy bast*rds!) but also gives "bad press" to the distribution when something that is managed in the main settings of the distribution just don't work. Also wanted to thank you for all the effort done for Raspberry Pi users with your work in this distribution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop... abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop. abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libcuda.so.1 abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libnvidia-encode.so.1 abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started On X11: --- abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
Well, as I stated above the fix is working and now VNC and RDP connections are working again. But I've tested gnome-remote-desktop under X11 and Wayland and there is a real performance problem in Wayland compared to X11 (key presseds are shown with a lag of seconds because refresh takes too much time). While you are connected to a gnome-remote-desktop session (using VNC or RDP) and only under Wayland the system log is populated several times per second with these messages that may be related to the performance problem: ... jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 14 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 106 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1933312 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 14 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 106 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:13 fpgrpi kernel: swiotlb_tbl_map_single: 82 callbacks suppressed ... These messages stops when you disconnect to gnome-remote-desktop. Please, tell me if it's necessary to open another bug for this problem or can be followed here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'.
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
Just updated to these packages: - gnome-remote-desktop (42.1.1-0ubuntu1) - libfreerdp2-2:arm64 (2.6.1+dfsg1-3ubuntu2.1) - libfreerdp-server2-2:arm64 (2.6.1+dfsg1-3ubuntu2.1) - libfreerdp-client2-2:arm64 (2.6.1+dfsg1-3ubuntu2.1) And VNC and RPD sharing are working now in arm64 (Raspberry Pi 4B). So bug seems to be fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: In Progress Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop... abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop. abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libcuda.so.1 abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libnvidia-encode.so.1 abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started On X11: --- abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions vanished abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 19. abr 25 00:12:18 fpgrpi systemd[2859]: Stopped GNOME Remote Desktop. abr 25 00:12:18 fpgrpi systemd[2859]: Starting GNOME Remote Desktop... abr 25 00:12:18 fpgrpi systemd[2859]: Started GNOME Remote Desktop. abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load libcuda.so.1 abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load libnvidia-encode.so.1 abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: RDP server started abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: VNC server
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
As a temporary (or final) solution just use another VNC or RDP Server. You can do that only if you use X11 because apart from gnome-remote- desktop there are no working desktop sharing utilities for Wayland. You've more info here: https://help.ubuntu.com/community/VNC/Servers For instance, I'm using vino VNC server, the old-but-gold sharing server for Ubuntu. I'm not only using it to remotely access an started user session. I also use it to access gdm remotely so I can start users sessions remotely directly from the greeter. This is something that I haven't managed to do with genome-remote-session because of it's way of store/access credentials. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: In Progress Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop... abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop. abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libcuda.so.1 abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libnvidia-encode.so.1 abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started On X11: --- abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions vanished abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 19. abr 25 00:12:18 fpgrpi systemd[2859]: Stopped GNOME Remote Desktop. abr 25 00:12:18 fpgrpi systemd[2859]: Starting GNOME Remote Desktop... abr 25 00:12:18 fpgrpi systemd[2859]: Started
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
This problem happens with transmission-gtk package. A workaround is to use transmission-qt package instead of transmission-gtk. With transmission-gtk, when you open the torrent's properties panel, apart from scramble the texts, buttons, etc, there are GTK related errors spammed every few milliseconds (can be seen with journalctl). This is an example of these errors: may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkLabel' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_label_get_text: assertion 'GTK_IS_LABEL (label)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_label_set_text: assertion 'GTK_IS_LABEL (label)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkTreeModel' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_tree_model_iter_nth_child: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_tree_model_iter_nth_child: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkToggleButton' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_toggle_button_get_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_block: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_toggle_button_set_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_unblock: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkToggleButton' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_toggle_button_get_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkSpinButton' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_spin_button_get_value_as_int: assertion 'GTK_IS_SPIN_BUTTON (spin_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_block: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_spin_button_set_value: assertion 'GTK_IS_SPIN_BUTTON (spin_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_unblock: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkToggleButton' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_toggle_button_get_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkSpinButton' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_spin_button_get_value_as_int: assertion 'GTK_IS_SPIN_BUTTON (spin_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_block: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_spin_button_set_value: assertion 'GTK_IS_SPIN_BUTTON (spin_button)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_unblock: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_block: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: invalid unclassed pointer in cast to 'GtkComboBox' may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_combo_box_get_model: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_combo_box_get_active_iter: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: gtk_tree_model_iter_nth_child: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38 fpgrpi transmission-gt[9098]: g_signal_handler_unblock: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed may 01 07:17:38 fpgrpi transmission-gt[9098]: instance with invalid (NULL) class pointer may 01 07:17:38
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
* How did you enable the sharing? Using the config page: see attached image. I'm using exactly the same configuration and OS in 3 computers: 2 amd64 and the arm64 Raspberry Pi. In the amd64 ones VNC works. It only fails in the arm64 Raspberry Pi. * The default protocol and suggested one is RDP, did you try if that works better? In my case RDP just doesn't work in any of my machines (neither amd64 nor arm64). The RDP server gives these errors when I try to connect: abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:631] [4496:5565] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312] abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313] abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [ERROR][com.winpr.sspi.NTLM] - Message Integrity Check (MIC) verification failed! abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [WARN][com.winpr.sspi] - CompleteAuthToken status SEC_E_MESSAGE_ALTERED [0x8009030F] abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [WARN][com.freerdp.core.nla] - CompleteAuthToken status SEC_E_MESSAGE_ALTERED [0x8009030F] abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [ERROR][com.freerdp.core.transport] - client authentication failure abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_INITIAL - rdp_server_accept_nego() fail abr 25 19:06:26 fpglinux gnome-remote-desktop-daemon[4496]: [19:06:26:731] [4496:5565] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 abr 25 19:06:26 fpglinux gnome-remote-de[4496]: Unable to check file descriptor, closing connection These errors may be related to this problem that I think is not solved in the Ubuntu current freerdp version: https://github.com/FreeRDP/FreeRDP/issues/7722 ** Bug watch added: freerdp-issues #7722 https://github.com/FreeRDP/FreeRDP/issues/7722 ** Attachment added: "Remote Access config" https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970139/+attachment/5583584/+files/Captura%20desde%202022-04-25%2019-31-43.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: Incomplete Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
I managed to get a crash file from apport. It's attached. ** Attachment added: "apport crash file" https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970139/+attachment/5583259/+files/_usr_libexec_gnome-remote-desktop-daemon.1026.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: New Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop... abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop. abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libcuda.so.1 abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libnvidia-encode.so.1 abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started On X11: --- abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions vanished abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 19. abr 25 00:12:18 fpgrpi systemd[2859]: Stopped GNOME Remote Desktop. abr 25 00:12:18 fpgrpi systemd[2859]: Starting GNOME Remote Desktop... abr 25 00:12:18 fpgrpi systemd[2859]: Started GNOME Remote Desktop. abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load libcuda.so.1 abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load libnvidia-encode.so.1 abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: RDP server started abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: VNC server started To manage notifications about this bug go to:
[Desktop-packages] [Bug 1970139] [NEW] VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
Public bug reported: # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop... abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop. abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libcuda.so.1 abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libnvidia-encode.so.1 abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started On X11: --- abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions vanished abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 19. abr 25 00:12:18 fpgrpi systemd[2859]: Stopped GNOME Remote Desktop. abr 25 00:12:18 fpgrpi systemd[2859]: Starting GNOME Remote Desktop... abr 25 00:12:18 fpgrpi systemd[2859]: Started GNOME Remote Desktop. abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load libcuda.so.1 abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load libnvidia-encode.so.1 abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: RDP server started abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: VNC server started ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: New Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
[Desktop-packages] [Bug 1947058] [NEW] Options missing in arm64 build compared to amd64 build
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 (3.28.1-6build2) and same Ubuntu version (21.10), where you can see the missing icon: This is the amd64 screenshot (OK): https://images2.imgbox.com/18/9c/E8pwQflW_o.png This is the arm64 screenshot (missing icon): https://images2.imgbox.com/7b/5b/atge11R3_o.png Details: arm64: -- root@fpgrpi:~# lsb_release -rd Description:Ubuntu 21.10 Release:21.10 root@fpgrpi:~# apt-cache policy gnome-todo gnome-todo: Instalados: 3.28.1-6build2 Candidato: 3.28.1-6build2 Tabla de versión: *** 3.28.1-6build2 500 500 http://ports.ubuntu.com/ubuntu-ports impish/main arm64 Packages 100 /var/lib/dpkg/status amd64: -- root@fpglinux:~# lsb_release -rd Description:Ubuntu 21.10 Release:21.10 root@fpglinux:~# apt-cache policy gnome-todo gnome-todo: Instalados: 3.28.1-6build2 Candidato: 3.28.1-6build2 Tabla de versión: *** 3.28.1-6build2 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gnome-todo (Ubuntu) Importance: Undecided Status: New ** Description changed: 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 (3.28.1-6build2) and same Ubuntu version (21.10), where you can see the missing icon: This is the amd64 screenshot (OK): - https://images2.imgbox.com/9c/a9/3CiIanbc_o.png + https://images2.imgbox.com/18/9c/E8pwQflW_o.png This is the arm64 screenshot (missing icon): https://images2.imgbox.com/7b/5b/atge11R3_o.png Details: arm64: -- root@fpgrpi:~# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@fpgrpi:~# apt-cache policy gnome-todo gnome-todo: - Instalados: 3.28.1-6build2 - Candidato: 3.28.1-6build2 - Tabla de versión: - *** 3.28.1-6build2 500 - 500 http://ports.ubuntu.com/ubuntu-ports impish/main arm64 Packages - 100 /var/lib/dpkg/status + Instalados: 3.28.1-6build2 + Candidato: 3.28.1-6build2 + Tabla de versión: + *** 3.28.1-6build2 500 + 500 http://ports.ubuntu.com/ubuntu-ports impish/main arm64 Packages + 100 /var/lib/dpkg/status amd64: -- root@fpglinux:~# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@fpglinux:~# apt-cache policy gnome-todo gnome-todo: - Instalados: 3.28.1-6build2 - Candidato: 3.28.1-6build2 - Tabla de versión: - *** 3.28.1-6build2 500 - 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages - 100 /var/lib/dpkg/status + Instalados: 3.28.1-6build2 + Candidato: 3.28.1-6build2 + Tabla de versión: + *** 3.28.1-6build2 500 + 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-todo in Ubuntu. https://bugs.launchpad.net/bugs/1947058 Title: Options missing in arm64 build compared to amd64 build Status in gnome-todo package in Ubuntu: New Bug description: 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 (3.28.1-6build2) and same Ubuntu version (21.10), where you can see the missing icon: This is the amd64 screenshot (OK): https://images2.imgbox.com/18/9c/E8pwQflW_o.png This is the arm64 screenshot (missing icon): https://images2.imgbox.com/7b/5b/atge11R3_o.png Details: arm64: -- root@fpgrpi:~# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@fpgrpi:~# apt-cache policy gnome-todo gnome-todo: Instalados: 3.28.1-6build2 Candidato: 3.28.1-6build2 Tabla de versión: *** 3.28.1-6build2 500 500 http://ports.ubuntu.com/ubuntu-ports impish/main arm64 Packages 100 /var/lib/dpkg/status amd64: -- root@fpglinux:~# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@fpglinux:~# apt-cache policy gnome-todo gnome-todo: Instalados: 3.28.1-6build2 Candidato: 3.28.1-6build2 Tabla de versión: *** 3.28.1-6build2 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to:
[Desktop-packages] [Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
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 "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" && echo
GJS works
[object Promise]
GJS works
2./ The error shown in every boot is gone.
3./ The indicator-multiload app is working as expected
So the bug seem to be fixed. Thanks and best regards.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
Fix Released
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Status in gjs source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script
threw an exception
[ Regression potential ]
Gjs apps are slower in starting up, or not act properly when / is not
a local location.
---
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 indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
multiload, Impossible to read image from path '/run/user/1026
/multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
TypeError: method Gio.File.read_async: At least 3 arguments required,
but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915929] Re: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop)
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 calendar sync with my google account and the
reported problem is gone. I also check that the calendar sync worked as
expected.
So the bug seem to be fixed. Thanks and best regards.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1915929
Title:
gnome-shell-calendar-server assert failure on arm64: double free or
corruption (fasttop)
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell source package in Focal:
Fix Committed
Status in gnome-shell source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
gnome-shell-calendar-server crashes (and it seems to happen more in
aarch64).
https://errors.ubuntu.com/problem/028fd7df90d750d70c7fea9719974347af67fa5a
https://errors.ubuntu.com/problem/33eeeda9b48baf59fe82b6b1f0aaa9465193b7f1
[ Test case ]
There's not a clear test case, but this is relevant:
- Configure a supported calendar in your online accounts
- GNOME shell should show your events in the calendar (under notifications
panel)
[ Regression potential ]
gnome-shell-calendar-server may leak memory.
---
M1 Mac mini
Parallels Ubuntu VM
ProblemType: CrashDistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.3-2ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic aarch64
ApportVersion: 2.20.11-0ubuntu58
Architecture: arm64
AssertionMessage: double free or corruption (fasttop)
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 17 04:34:36 2021
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-calendar-server
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
b'org.gnome.desktop.peripherals.keyboard' b'numlock-state' b'true'
InstallationDate: Installed on 2021-02-17 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha arm64 (20210217)
ProcCmdline: /usr/libexec/gnome-shell-calendar-server
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
LANG=en_US.UTF-8
RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1
Signal: 6SourcePackage: gnome-shell
StacktraceTop:
__libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x81245180
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
malloc_printerr (str=str@entry=0x81240c08 "double free or corruption
(fasttop)") at malloc.c:5389
_int_free (av=, p=0xe9eee300, have_lock=0) at
malloc.c:4298
g_variant_builder_clear () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
?? ()
Title: gnome-shell-calendar-server assert failure: double free or corruption
(fasttop)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1915929/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
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 Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
Fix Released
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Status in gjs source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script
threw an exception
[ Regression potential ]
Gjs apps are slower in starting up, or not act properly when / is not
a local location.
---
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 indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
multiload, Impossible to read image from path '/run/user/1026
/multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
TypeError: method Gio.File.read_async: At least 3 arguments required,
but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
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 show:
abr 23 02:45:40 fpglinux gnome-shell[1730]: value "nan" of type 'gfloat' is
invalid or out of range for property 'x' of type 'gfloat'
abr 23 02:45:40 fpglinux gnome-shell[1730]: value "nan" of type 'gfloat' is
invalid or out of range for property 'y' of type 'gfloat'
abr 23 02:45:40 fpglinux gnome-shell[1730]: value "-inf" of type 'gfloat' is
invalid or out of range for property 'width' of type 'gfloat'
abr 23 02:45:40 fpglinux gnome-shell[1730]: value "-inf" of type 'gfloat' is
invalid or out of range for property 'height' of type 'gfloat'
So it's probably happening since ages...
Thank you very much for the quick fix and happy releasing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Status in gjs source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script
threw an exception
[ Regression potential ]
Gjs apps are slower in starting up, or not act properly when / is not
a local location.
---
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 indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
multiload, Impossible to read image from path '/run/user/1026
/multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
TypeError: method Gio.File.read_async: At least 3 arguments required,
but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
BTW: as I said the problem is solved with the proposed builds.
So, the indicator-multiload app is working as expected. But I just
realized that is throwing another messages at its start, messages that
it's not throwing in Ubuntu 20.10 groovy. These are the messages:
amd64:
--
abr 23 02:54:52 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 'gfloat'
abr 23 02:54:52 fprietog-VirtualBox gnome-shell[1339]: JS ERROR: Exception in
callback for signal: shown: Error: Wrong type number; float expected. But it's
out of range: -Infinity
_init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16
_easeActor@resource:///org/gnome/shell/ui/environment.js:155:15
init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19
_syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21
_init/this._overviewShownId<@resource:///org/gnome/shell/ui/workspacesView.js:396:18
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
_showDone@resource:///org/gnome/shell/ui/overview.js:604:14
onComplete@resource:///org/gnome/shell/ui/overview.js:589:36
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:85:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:168:64
arm64:
--
abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is
invalid or out of range for property 'x' of type 'gfloat'
abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is
invalid or out of range for property 'y' of type 'gfloat'
abr 23 00:18:31 fpgrpi gnome-shell[1494]: JS ERROR: Exception in callback for
signal: shown: Error: Wrong type number; float expected. But it's out of range:
-Infinity
_init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16
_easeActor@resource:///org/gnome/shell/ui/environment.js:155:15
init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19
_syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21
_init/this._overviewShownId<@resource:///org/gnome/shell/ui/workspacesView.js:396:18
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
_showDone@resource:///org/gnome/shell/ui/overview.js:604:14
onComplete@resource:///org/gnome/shell/ui/overview.js:589:36
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:85:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:168:64
abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is
invalid or out of range for property 'x' of type 'gfloat'
abr 23 00:18:31 fpgrpi gnome-shell[1494]: value "nan" of type 'gfloat' is
invalid or out of range for property 'y' of type 'gfloat'
abr 23 00:18:31 fpgrpi gnome-shell[1494]: JS ERROR: Error: Wrong type number;
float expected. But it's out of range: -Infinity
_init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16
_easeActor@resource:///org/gnome/shell/ui/environment.js:155:15
init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19
_syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21
_updateWorkspacesActualGeometry/this._syncActualGeometryLater<@resource:///org/gnome/shell/ui/workspacesView.js:716:22
But, as I said, I think these messages are not having impact in the
execution of indicator-multiload app. At least I didn't notice any
problem.
Just wanted to comment it, just in case.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Status in gjs source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396:
[Desktop-packages] [Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
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 Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Status in gjs source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script
threw an exception
[ Regression potential ]
Gjs apps are slower in starting up, or not act properly when / is not
a local location.
---
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 indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
multiload, Impossible to read image from path '/run/user/1026
/multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
TypeError: method Gio.File.read_async: At least 3 arguments required,
but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
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-2ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports hirsute/main arm64 Packages
- libgjs0g_1.67.2-2ubuntu2_arm64.deb
fprietog@fpgrpi:~$ apt-cache policy libgjs0g
libgjs0g:
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-2ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports hirsute/main arm64 Packages
And, after reboot, the problem reported is solved:
1./ Test case:
fprietog@fpgrpi:~$ gjs -c
"imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype, 'delete_async',
'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" && echo
GJS works
[object Promise]
GJS works
2./ The error shown in every boot as also gone.
3./ The indicator-multiload app now is working as expected
I'll test amd64 build when available.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Status in gjs source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script
threw an exception
[ Regression potential ]
Gjs apps are slower in starting up, or not act properly when / is not
a local location.
---
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 indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
multiload, Impossible to read image from path '/run/user/1026
/multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
TypeError: method Gio.File.read_async: At least 3 arguments required,
but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923267] Re: indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1
Unfortunately I still got the same problem with gnome-shell-extension- appindicator 35-1 installed. I don't think that this will be related to gnome-shell-extension- appindicator because I'm also getting this error message every boot and it that seems to be the same problem in a different app 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/shell/ui/main.js:303:13 _startupAnimationComplete@resource:///org/gnome/shell/ui/layout.js:733:14 onComplete@resource:///org/gnome/shell/ui/layout.js:711:36 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:85:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:168:64 I can assure that with libglib2.0-0, libglib2.0-bin and libglib2.0-data version 2.67.5-2 it works, but with version to 2.68.0-1 it doesn't. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1923267 Title: indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: 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 indicator-multiload (0.4-0ubuntu5) doesn't work showing only three dots (...) instead of the graphic expected. It's throwing error messages to the system journal every second or so (depends of the refresh interval selected in the app settings): abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]: multiload, Impossible to read image from path '/run/user/1026 /multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png': TypeError: method Gio.File.read_async: At least 3 arguments required, but only 2 passed Don't know if this is a documented change of that method and the bug should be open for the indicator-multiload app. Please, if that's the case just let me know to do it. Thanks and best reagrds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1923267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923267] [NEW] indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1
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 indicator-multiload (0.4-0ubuntu5) doesn't work showing only three dots (...) instead of the graphic expected. It's throwing error messages to the system journal every second or so (depends of the refresh interval selected in the app settings): abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]: multiload, Impossible to read image from path '/run/user/1026/multiload-icons- Wc8kck/icons/indicator-multiload-graphs-0.png': TypeError: method Gio.File.read_async: At least 3 arguments required, but only 2 passed Don't know if this is a documented change of that method and the bug should be open for the indicator-multiload app. Please, if that's the case just let me know to do it. Thanks and best reagrds ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1923267 Title: indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 Status in glib2.0 package in Ubuntu: New Bug description: 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 indicator-multiload (0.4-0ubuntu5) doesn't work showing only three dots (...) instead of the graphic expected. It's throwing error messages to the system journal every second or so (depends of the refresh interval selected in the app settings): abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]: multiload, Impossible to read image from path '/run/user/1026 /multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png': TypeError: method Gio.File.read_async: At least 3 arguments required, but only 2 passed Don't know if this is a documented change of that method and the bug should be open for the indicator-multiload app. Please, if that's the case just let me know to do it. Thanks and best reagrds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1923267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580537] Re: LibreOffice with ambiance theme and breeze icon style is unusable
@Björn Michaelsen; the fixed pic you posted looks very nice. Hope the fix reach the repo soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1580537 Title: LibreOffice with ambiance theme and breeze icon style is unusable Status in libreoffice package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Fix Committed Bug description: Until today i didn't use LibreOffice on Ubuntu 16.04. I opened it today and i see menu/icon bar totally unusable with Ambiance theme and default Breeze style. (image attached) The version installed is 5.1.2-0ubuntu1. I did upgrade from 14.04 to 16.04 with some issues. Changing from Breeze to Human is usable but fugly. No issue with Radiance theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1580537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445595] Re: Empty trash from Launcher results in Nautilus window opening
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 when it's open and the trash is emptied. Now it's worse because even if nautilus is closed (I mean, no nautilus windows are currently opened) and you empty trash, nautilus is opened and focused. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1445595 Title: Empty trash from Launcher results in Nautilus window opening Status in One Hundred Papercuts: New Status in Unity: New Status in nautilus package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: Test case: - Add a file to trash if none already - Right click on Unity launcher trash icon click on Empty Trash option - Nautilus open a window @ home folder When selecting 'Empty trash' from the launcher, I get a dialog to confirm the deletion and a Nautilus window. When emptying trash from Nautilus window, I get only a confirmation dialog as expected. Expected behavior: - Only confirmation dialog pops up To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1445595/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445595] Re: Empty Trash Results in File Windows Opening
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 Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1445595 Title: Empty Trash Results in File Windows Opening Status in One Hundred Papercuts: New Status in Unity: New Status in nautilus package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: *Test case: Add a file to trash if none already Right click on Unity launcher trash icon click on Empty Trash option nautilus open a window @ home folder. When selecting 'empty trash' from the launcher I get a dialog to confirm the deletion and a file window. When emptying trash from nautilus window only get confirmation dialog as expected. Expected behavior: - Only confirm dialog pop up. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1445595/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
