[Desktop-packages] [Bug 2002845] Re: debhelper 13.11.4ubuntu1 broke dh-translations
I deleted my debhelper PPA. The changes are available here:
https://launchpad.net/ubuntu/+source/debhelper/13.11.4ubuntu2
but OTOH they are about to be reverted via debhelper 13.11.4ubuntu3.
--
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/2002845
Title:
debhelper 13.11.4ubuntu1 broke dh-translations
Status in debhelper package in Ubuntu:
Fix Committed
Status in gnome-control-center package in Ubuntu:
Invalid
Status in gnome-text-editor package in Ubuntu:
Invalid
Status in pkgbinarymangler package in Ubuntu:
Fix Released
Bug description:
Today's debhelper 13.11.4ubuntu1 merge broke dh-translations.
https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1
gnome-text-editor build log excerpt
---
dh_translations
Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu'
--targets |
jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm
line 518.
dh_translations: error: exec (for cmd: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'") failed: No such file or directory
dh_translations: error: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'" returned exit code 25
Other Info
--
Gunnar identified the bad commit as
https://salsa.debian.org/debian/debhelper/-/commit/62a8608
https://launchpad.net/~gunnarhj/+archive/ubuntu/debhelper/+packages
https://pastebin.ubuntu.com/p/P8qM2sHn9C/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/2002845/+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 2002680] Re: "Sharing Options" not translated to local language
The label "Sharing Options" will be shown translated in lunar at next update of the language packs. https://translations.launchpad.net/ubuntu/lunar/+source/nautilus- share/+pots/nautilus-share/ru?search=sharing+options ** Changed in: ubuntu-translations Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/2002680 Title: "Sharing Options" not translated to local language Status in Ubuntu Translations: Fix Released Status in nautilus-share package in Ubuntu: Fix Released Bug description: after installing nautilus-share the context entry for sharing is inconsistent with system language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/2002680/+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 2000937] Re: DING settings values shown untranslated
$ dpkg-query -W language-pack-gnome-fr-base language-pack-gnome-fr-base 1:23.04+20230106 $ echo $(LANGUAGE=fr gettext -d gnome-control-center-2.0 'Ubuntu Desktop') Bureau Ubuntu ** Changed in: ubuntu-translations Status: Fix Committed => Fix Released -- 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/2000937 Title: DING settings values shown untranslated Status in Ubuntu Translations: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Ubuntu 22.10 ; Gnome 43.0 Hello, There is a translation problem (missing?) in gnome-control-center. See image attached. Regards, Roxfr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/2000937/+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 1994435] Re: Proprietary NVIDIA drivers stopped working as of 10/24/22 update
I can confirm the original .sh NVIDIA driver works well. After uninstalling ubuntu nvidia driver, disabling nouveau, I installed .sh driver downloaded from NVIDIA pages + nvidia-prime. Everything works fine now. Ubuntu made some very bad bug in their packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1994435 Title: Proprietary NVIDIA drivers stopped working as of 10/24/22 update Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Ubuntu Release: 22.04.1.LTS Problem: On 10/24/22, I installed the latest Ubuntu 22.04.1 LTS updates. I don't know what was updated, but many of the packages had "oem" or "oracle" in their names, which I don't remember seeing before. Before updating, I had a NVIDIA driver from the "Software & Updates/Additional Drivers" list installed and I was using X11. I don't remember the driver version number, but it was the highest. After updating, Settings/About/Graphics changed from a GeForce RTX 2080 Ti to "llvmpipe (LLVM 13.0.1, 256 bits)". Windowing system was still X11. My three-monitor setup reverted to one monitor, and the display was of low resolution. I tried proprietary NVIDIA drivers 515, 510, and 470, but none restored the system to three monitors and high resolution. However, the Nouveau driver did restore the system. Settings/About/Graphics changed to NV162. Work-Around: I am now using the driver installed via "sudo sh NVIDIA- Linux-x86_64-515.76.run", from NVIDIA's website. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1994435/+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 1994435] Re: Proprietary NVIDIA drivers stopped working as of 10/24/22 update
No version if nvidia driver is working for my laptop HP HP ZBook Fury 15.6 inch G8 Mobile Workstation PC/8870, BIOS T95 Ver. 01.11.00 10/17/2022. It also worked before. Now I get: [ 10.159857] [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to allocate NvKmsKapiDevice [ 10.160067] [drm:nv_drm_probe_devices [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to register device -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1994435 Title: Proprietary NVIDIA drivers stopped working as of 10/24/22 update Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Ubuntu Release: 22.04.1.LTS Problem: On 10/24/22, I installed the latest Ubuntu 22.04.1 LTS updates. I don't know what was updated, but many of the packages had "oem" or "oracle" in their names, which I don't remember seeing before. Before updating, I had a NVIDIA driver from the "Software & Updates/Additional Drivers" list installed and I was using X11. I don't remember the driver version number, but it was the highest. After updating, Settings/About/Graphics changed from a GeForce RTX 2080 Ti to "llvmpipe (LLVM 13.0.1, 256 bits)". Windowing system was still X11. My three-monitor setup reverted to one monitor, and the display was of low resolution. I tried proprietary NVIDIA drivers 515, 510, and 470, but none restored the system to three monitors and high resolution. However, the Nouveau driver did restore the system. Settings/About/Graphics changed to NV162. Work-Around: I am now using the driver installed via "sudo sh NVIDIA- Linux-x86_64-515.76.run", from NVIDIA's website. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1994435/+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 1999100] Re: Update gnome-characters to 43.1
I'm removing the tag since glib2.0 is ready now. ** Tags removed: block-proposed block-proposed-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1999100 Title: Update gnome-characters to 43.1 Status in gnome-characters package in Ubuntu: Fix Released Status in gnome-characters source package in Kinetic: Fix Committed Bug description: NOTE TO SRU TEAM Please accept the glib2.0 SRU first. To enable the new feature to work best, I have added a Build-Depends (which results in a Depends) on the new glib version. Impact -- There is a new bugfix release in the stable 43 series https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/43.1/NEWS This adds one new feature: new emoji and Unicode characters from Unicode 15. Test Case 1 --- Install the update Open the Characters app. Select an emoji character and click Copy Character Paste the emoji somewhere. You should see the emoji you pasted. Test Case 2 --- Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ (This is Test Case 3 (Extra) from https://launchpad.net/bugs/1999098) What Could Go Wrong --- GNOME Characters is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME It is installed by default in Ubuntu Desktop and Ubuntu Budgie. Other Info -- Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 glib and gnome-characters are the only 2 late pieces that the Ubuntu Desktop team plans to SRU for Ubuntu 22.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1999100/+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 2002228] Re: incorrect maximum window geometry on secondary monitor makes contextmenu of gtk4 apps unusable
hmm, just upgraded to 23.04 and its fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2002228 Title: incorrect maximum window geometry on secondary monitor makes contextmenu of gtk4 apps unusable Status in gtk4 package in Ubuntu: New Status in sway package in Ubuntu: New Bug description: since upgrade to 22.10 gtk4 apps like nautilus on sway on the external monitors are restricted to size of the resolution of the first monitor (which is the laptop lcd, hence smaller) which results in broken apps contextmenu (like renaming files in nautilus is impossible). There is a bugreport in sway for it https://github.com/swaywm/sway/issues/7000 but i dont quite understand where the correct fix should be located: sway, wlroots, gtk4? However there seems to be a fix (workaround) for gtk4: https://gitlab.gnome.org/GNOME/gtk/-/issues/5402 -> https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4790 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: sway 1.7-5 [modified: usr/share/wayland-sessions/sway.desktop] ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Jan 8 01:04:27 2023 InstallationDate: Installed on 2022-03-24 (290 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: sway UpgradeStatus: Upgraded to kinetic on 2022-10-20 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2002228/+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 2002886] [NEW] Can't copy and paste from Geany (and SciTE?) in Wayland with GTK 3.24.35
Public bug reported: With GTK 3.24.35, when running under Wayland, it's not possible to copy and paste from Geany. (Others report the same issue with SciTE, which also uses the Scintilla editor.) The Geany upsteam bug isolated the issue to a GTK change (https://github.com/geany/geany/issues/3345#issuecomment-1360370992). The GTK bug (https://gitlab.gnome.org/GNOME/gtk/-/issues/5397) was resolved (https://gitlab.gnome.org/GNOME/gtk/-/commit/eca445672a48ac4a870790efa63339f8d974c2fd) and the fix is in GTK 3.24.36. I installed the libgtk-3-0_3.24.36-1_amd64.deb and libgtk-3-common_3.24.36-1_all.deb packages from Debian on a Lunar test system and this did resolve the issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libgtk-3-0 3.24.35-3ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jan 14 14:22:01 2023 InstallationDate: Installed on 2022-12-28 (17 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar uec-images wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2002886 Title: Can't copy and paste from Geany (and SciTE?) in Wayland with GTK 3.24.35 Status in gtk+3.0 package in Ubuntu: New Bug description: With GTK 3.24.35, when running under Wayland, it's not possible to copy and paste from Geany. (Others report the same issue with SciTE, which also uses the Scintilla editor.) The Geany upsteam bug isolated the issue to a GTK change (https://github.com/geany/geany/issues/3345#issuecomment-1360370992). The GTK bug (https://gitlab.gnome.org/GNOME/gtk/-/issues/5397) was resolved (https://gitlab.gnome.org/GNOME/gtk/-/commit/eca445672a48ac4a870790efa63339f8d974c2fd) and the fix is in GTK 3.24.36. I installed the libgtk-3-0_3.24.36-1_amd64.deb and libgtk-3-common_3.24.36-1_all.deb packages from Debian on a Lunar test system and this did resolve the issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libgtk-3-0 3.24.35-3ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jan 14 14:22:01 2023 InstallationDate: Installed on 2022-12-28 (17 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2002886/+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 2000937] Re: DING settings values shown untranslated
This bug was fixed in the package gnome-control-center - 1:44~alpha-0ubuntu1 --- gnome-control-center (1:44~alpha-0ubuntu1) lunar; urgency=medium [ Jeremy Bicha ] * New upstream release * debian/control.in: Bump minimum GTK4 to 4.8 and libnma-gtk4 to 1.10.2 * Stop disabling the Device Security panel * Revert commit that hides Device Security panel when chassis_type is empty * Refresh patches * Update patches to drop deprecated gtk_widget_show/hide [ Gunnar Hjalmarsson ] * Make "Color" in "Appearance" view translatable (LP: #2000937) * Use a context aware gettext function in the Ubuntu panel (LP: #2000937) -- Jeremy Bicha Fri, 13 Jan 2023 11:48:57 -0500 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- 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/2000937 Title: DING settings values shown untranslated Status in Ubuntu Translations: Fix Committed Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Ubuntu 22.10 ; Gnome 43.0 Hello, There is a translation problem (missing?) in gnome-control-center. See image attached. Regards, Roxfr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/2000937/+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 2002609] Re: [SRU] Disable pressure for not detecting contact size
This bug was fixed in the package libinput - 1.22.0-1ubuntu1 --- libinput (1.22.0-1ubuntu1) lunar; urgency=medium * Disable pressure for not detecting contact size (LP: #2002609) - d/p/0001-quirks-add-quirks-for-Dell-Precision5680-Touchpad.patch Disable the pressure handling for the touchpad. -- Kai-Chuan Hsieh Thu, 12 Jan 2023 16:20:42 +0800 ** Changed in: libinput (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2002609 Title: [SRU] Disable pressure for not detecting contact size Status in OEM Priority Project: New Status in libinput package in Ubuntu: Fix Released Status in libinput source package in Jammy: Fix Committed Status in libinput source package in Kinetic: Fix Committed Bug description: [ Impact ] * Dell's platform has a touchpad report pressure capability * The predefined threshold for the touchpad cause the user experience bad * Disable pressure event handling to align with upstream [ Test Plan ] * on Dell precision 5680 with touchpad vid:0x27c6 pid:0x0f60 * check left/right button * check 2 fingers scrolling * check 1 finger drag and drop * check 2 fingers drag and drop [ Where problems could occur ] * The quirk match the PID VID only, it won't impact other touchpad [ Other Info ] * https://gitlab.freedesktop.org/libinput/libinput/-/commit/29a49e968e67eb7bf6d63c9f93b06ee983772018 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2002609/+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 2002680] Re: "Sharing Options" not translated to local language
This bug was fixed in the package nautilus-share - 0.7.5-0.3 --- nautilus-share (0.7.5-0.3) unstable; urgency=medium * Non-maintainer upload * Add support for language packs when building for Ubuntu (LP: #2002680) * Update po/POTFILES.in due to new build system - patch forwarded upstream * Bump Standards-Version to 4.6.2 -- Gunnar Hjalmarsson Fri, 13 Jan 2023 13:57:38 +0100 ** Changed in: nautilus-share (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/2002680 Title: "Sharing Options" not translated to local language Status in Ubuntu Translations: Incomplete Status in nautilus-share package in Ubuntu: Fix Released Bug description: after installing nautilus-share the context entry for sharing is inconsistent with system language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/2002680/+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 2002845] Re: debhelper 13.11.4ubuntu1 broke dh-translations
This bug was fixed in the package pkgbinarymangler - 150
---
pkgbinarymangler (150) lunar; urgency=medium
* dh_translations:
- After the latest debhelper change, the qx_cmd() function from
Dh_Lib.pm does not work in the context in which it's used in
dh_translations. So the previous qx_cmd() function has been
copied into dh_translations under the name qx_meson_cmd()
(LP: #2002845).
* Failing tests disabled in test/run:
- test_debian_changelog_truncation
- test_native_changelog_truncation
- test_ppa_debian_changelog
-- Gunnar Hjalmarsson Sat, 14 Jan 2023 10:59:26
+0100
** Changed in: pkgbinarymangler (Ubuntu)
Status: Fix Committed => Fix Released
--
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/2002845
Title:
debhelper 13.11.4ubuntu1 broke dh-translations
Status in debhelper package in Ubuntu:
Fix Committed
Status in gnome-control-center package in Ubuntu:
Invalid
Status in gnome-text-editor package in Ubuntu:
Invalid
Status in pkgbinarymangler package in Ubuntu:
Fix Released
Bug description:
Today's debhelper 13.11.4ubuntu1 merge broke dh-translations.
https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1
gnome-text-editor build log excerpt
---
dh_translations
Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu'
--targets |
jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm
line 518.
dh_translations: error: exec (for cmd: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'") failed: No such file or directory
dh_translations: error: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'" returned exit code 25
Other Info
--
Gunnar identified the bad commit as
https://salsa.debian.org/debian/debhelper/-/commit/62a8608
https://launchpad.net/~gunnarhj/+archive/ubuntu/debhelper/+packages
https://pastebin.ubuntu.com/p/P8qM2sHn9C/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/2002845/+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 905587] Re: [ICH - Intel 82801AA-ICH, playback] No sound at all
Hi! I am still facing this issue. Please guide me here, I am new to
linux environments. Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/905587
Title:
[ICH - Intel 82801AA-ICH, playback] No sound at all
Status in alsa-driver package in Ubuntu:
Expired
Bug description:
using rhythmbox on ubuntu 12.04 updated 16-12-2011, trying to play m4a
file no sound. Tried to use sound settings applet, ouput tab, changing
output sound from amplifier to no amplifier caused the crashm
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.24+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-3.9-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel
82801AA-ICH]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 1.90-0ubuntu1
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bertadmin 17553 F pulseaudio
Card0.Amixer.info:
Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with STAC9700,83,84 at irq 5'
Mixer name : 'SigmaTel STAC9700,83,84'
Components : 'AC97a:83847600'
Controls : 34
Simple ctrls : 24
Date: Fri Dec 16 21:14:31 2011
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386
(20111209.1)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH
successful
Symptom_Card: Internal Audio - Intel 82801AA-ICH
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [ICH - Intel 82801AA-ICH, playback] No sound at all
UpgradeStatus: Upgraded to precise on 2011-12-10 (6 days ago)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/905587/+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 1990563] Re: Some maximized/fullscreen windows appear on both monitors
Problem is that there are so far no plans to release it for 22.10. It seems 23.04 will indeed have to 43.2 https://code.launchpad.net/ubuntu/+source/mutter Let's hope it fixes it, or another year-long iteration will be necessary. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1990563 Title: Some maximized/fullscreen windows appear on both monitors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: I have a dual monitor setup, with external monitor configured as primary. When I maximize certain windows on the secondary monitor, a copy of the same window appears on the primary monitor (see first attached video). It happens with some apps, not with all of them. For example, it happens with IntelliJ IDEA (Java app) and Spotify (presumably Electron app), not with Gnome Text Editor, Gnome Terminal, Chrome or Firefox, for instance. A very similar situation occurs when taking a screenshot with Flameshot, though in the opposite way: a copy of the primary monitor appears on the secondary (see second attached video). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mutter 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Sep 22 14:37:37 2022 InstallationDate: Installed on 2018-12-14 (1378 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: mutter UpgradeStatus: Upgraded to kinetic on 2022-09-02 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1990563/+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 2002882] [NEW] nautilus sometimes gets stuck when opening a folder and never shows the files inside
Public bug reported: Observed behaviour: open a directory (in my case, containing 20 photos, ~200 MB in total). Nautilus shows activity (the "Loading..." indicator is active and animated), but it just stays that way indefinitely (2-3 minutes now), without showing the files. Expected behaviour: Effectively immediately show the contents of a directory with ~20 files. Repeatability: infrequently, maybe 5% of the time Workarounds: go to the parent dir, come back to the subdirectory in question and its contents show up immediately, without issues. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 14 18:51:07 2023 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'198' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified_with_time', 'starred']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2022-11-03 (72 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2023-01-14 18-50-51.png" https://bugs.launchpad.net/bugs/2002882/+attachment/5641382/+files/Screenshot%20from%202023-01-14%2018-50-51.png -- 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/2002882 Title: nautilus sometimes gets stuck when opening a folder and never shows the files inside Status in nautilus package in Ubuntu: New Bug description: Observed behaviour: open a directory (in my case, containing 20 photos, ~200 MB in total). Nautilus shows activity (the "Loading..." indicator is active and animated), but it just stays that way indefinitely (2-3 minutes now), without showing the files. Expected behaviour: Effectively immediately show the contents of a directory with ~20 files. Repeatability: infrequently, maybe 5% of the time Workarounds: go to the parent dir, come back to the subdirectory in question and its contents show up immediately, without issues. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 14 18:51:07 2023 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'198' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified_with_time', 'starred']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2022-11-03 (72 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2002882/+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 notificat
[Desktop-packages] [Bug 1999098] Re: Update glib to 2.74.3
The autopkgtests all pass now. I installed glib 2.74.3-0ubuntu1, restarted my computer and ensured that epiphany-browser, the file browser and the terminal all appear to work correctly. I also installed gnome-characters 43.1-0ubuntu1 and verified that I was able to search for the moose emoji and copy it. ** Tags removed: verification-needed verification-needed-kinetic ** Tags added: verification-done verification-done-kinetic -- 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/1999098 Title: Update glib to 2.74.3 Status in glib2.0 package in Ubuntu: Fix Committed Status in glib2.0 source package in Kinetic: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.74 series The current release in Ubuntu 22.10 is 2.74.0 https://gitlab.gnome.org/GNOME/glib/-/blob/2.74.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser Test Case 3 (Extra) -- Install gnome-characters 43.1. (This is being SRU'd, but the version from Lunar also works.) Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ With glib 2.74.0, the moose emoji won't be searchable but it does show in the Animals category. What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 glib and gnome-characters are the only 2 late pieces that the Ubuntu Desktop team plans to SRU for Ubuntu 22.10. Ubuntu 23.04 has 2.74.2 with the commits from 2.74.3 backported so they are functionally equivalent. Ubuntu 23.04 will get newer glib versions before 23.04 is released. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1999098/+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
Sorry for the incomplete search... Apparently this is sort of a "known bug", due to the fact that when in "auto-login" the keyring is not unlocked then VNC server cannot access the stored password and creates a new random one. https://askubuntu.com/questions/1403943/22-04-remote-desktop-sharing- authentication-password-changes-every-reboot There is a semi-insecure fix proposed. I'll try that until a better fix is proposed! -- 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 fpgr
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
New test on January 14th 2023! VNC from another Ubuntu machine using Remmina as client is now working with severe limitations. Documentation I found after some more research: - Probably a security feature: Remote Desktop does NOT work when: - the session is locked - even when screen is blanked via for instance the command dbus-send --session --dest=org.gnome.ScreenSaver --type=method_call /org/gnome/ScreenSaver org.gnome.ScreenSaver.SetActive boolean:true That is understandable and would not be a blocker on my use case. Another thing, though that is a blocker, is that the password keeps changing! Steps to reproduce: - Switch remote desktop on - Allow VNC (legacy method), tick "requires a password" - Set your user ID and password - Click on the button to view your password, and check this is indeed what you have set - Without locking your session or even blanking the screen, connect from another Ubuntu machine (Remmina-VNC) typing your ID and Password - This should now work - Now reboot your Raspberry Pi 4 Ubuntu 22.04 - Display again the settings about remote connection - Click on the button to view the password - It is now a whole new password apparently randomly set at start up. So now, either you need a method to get that password from command line, or set it back from command line (since you can still SSH and fortunately the SSH password is not messed around the same) or you are blocked! Questions: - Is this resetting of the remote password intended? - If so, how can we retrieve/reset it from command line (gsettings, dconf,...) - If not, should I file a different bug report? -- 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-packages] [Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
The Device Security panel has been simplified in GNOME 44 Alpha and Ubuntu 23.04 no longer disables showing the panel. https://launchpad.net/ubuntu/+source/gnome-control- center/1:44~alpha-0ubuntu1 -- 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/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently Status in gnome-control-center package in Ubuntu: Fix Released Bug description: GNOME 43 added a new Device Security feature in the Settings app. You can access it in gnome-control-center 1:43~beta-1ubuntu1 1. Open the Settings app 2. Click Privacy then Device Security The Security Events aren't clickable. A default Ubuntu install only gets us "Security Level 1". The highest level is "Security Level 3". There isn't anything an Ubuntu user can do to get to a higher security level from the Device Security screen. If a user attempts to get their system to a higher security level, I think they could break their system since this isn't something we currently support. Therefore, I think we ought to hide/disable the screen for Ubuntu 22.10. We can work towards better integrating this screen for Ubuntu in future releases. I'm attaching several screenshots although it's worth trying out the feature for yourself too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+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 2002869] Re: "ctrl:swapcaps" doesn't swap shift+capslock and shift+ctrl
Thanks for your report!
That kind of issue is really upstream in nature, and nothing we would
like to change in Ubuntu only. So it would be great if you could submit
an upstream issue too:
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-
config/-/issues
If you do, please add a comment here with the URL.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/2002869
Title:
"ctrl:swapcaps" doesn't swap shift+capslock and shift+ctrl
Status in xkeyboard-config package in Ubuntu:
New
Bug description:
Ubuntu: 22.10
xkb-data: 2.35.1-1
keyboard layout: jp106
I enable a xkb option "ctrl:swapcaps" and often use shift+ctrl
modifier key combinations like shift+ctrl+T.
Expected:
Both pressing [shift]+[capslock] and [capslock]+[shift] should work as
shift+ctrl modifier.
What happened:
[capslock]+[shift] works as expected, but [shift]+[capslock] still
works as shift+capslock.
This behavior is very confusing and annoying to me.
Workaround:
The problem can be avoided by editing /usr/share/X11/xkb/symbols/ctrl
as follows.
--- ctrl.orig 2022-02-09 02:13:55.0 +0900
+++ ctrl 2023-01-14 18:57:15.589534502 +0900
@@ -14,7 +14,7 @@
// Swap the functions of the CapsLock key and the left Ctrl key.
partial modifier_keys
xkb_symbols "swapcaps" {
-replace key { [ Control_L ] };
+replace key { [ Control_L, Control_L ] };
replace key { [ Caps_Lock ] };
modifier_map Control { };
modifier_map Lock { };
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/2002869/+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 2002869] [NEW] "ctrl:swapcaps" doesn't swap shift+capslock and shift+ctrl
Public bug reported:
Ubuntu: 22.10
xkb-data: 2.35.1-1
keyboard layout: jp106
I enable a xkb option "ctrl:swapcaps" and often use shift+ctrl modifier
key combinations like shift+ctrl+T.
Expected:
Both pressing [shift]+[capslock] and [capslock]+[shift] should work as
shift+ctrl modifier.
What happened:
[capslock]+[shift] works as expected, but [shift]+[capslock] still works
as shift+capslock.
This behavior is very confusing and annoying to me.
Workaround:
The problem can be avoided by editing /usr/share/X11/xkb/symbols/ctrl as
follows.
--- ctrl.orig 2022-02-09 02:13:55.0 +0900
+++ ctrl2023-01-14 18:57:15.589534502 +0900
@@ -14,7 +14,7 @@
// Swap the functions of the CapsLock key and the left Ctrl key.
partial modifier_keys
xkb_symbols "swapcaps" {
-replace key { [ Control_L ] };
+replace key { [ Control_L, Control_L ] };
replace key { [ Caps_Lock ] };
modifier_map Control { };
modifier_map Lock { };
** Affects: xkeyboard-config (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/2002869
Title:
"ctrl:swapcaps" doesn't swap shift+capslock and shift+ctrl
Status in xkeyboard-config package in Ubuntu:
New
Bug description:
Ubuntu: 22.10
xkb-data: 2.35.1-1
keyboard layout: jp106
I enable a xkb option "ctrl:swapcaps" and often use shift+ctrl
modifier key combinations like shift+ctrl+T.
Expected:
Both pressing [shift]+[capslock] and [capslock]+[shift] should work as
shift+ctrl modifier.
What happened:
[capslock]+[shift] works as expected, but [shift]+[capslock] still
works as shift+capslock.
This behavior is very confusing and annoying to me.
Workaround:
The problem can be avoided by editing /usr/share/X11/xkb/symbols/ctrl
as follows.
--- ctrl.orig 2022-02-09 02:13:55.0 +0900
+++ ctrl 2023-01-14 18:57:15.589534502 +0900
@@ -14,7 +14,7 @@
// Swap the functions of the CapsLock key and the left Ctrl key.
partial modifier_keys
xkb_symbols "swapcaps" {
-replace key { [ Control_L ] };
+replace key { [ Control_L, Control_L ] };
replace key { [ Caps_Lock ] };
modifier_map Control { };
modifier_map Lock { };
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/2002869/+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 2002845] Re: debhelper 13.11.4ubuntu1 broke dh-translations
The packages mentioned in this bug (gnome-control-center and gnome-text-
editor) build fine now, and so does nautilus-share which I had uploaded.
I have removed the block-proposed tag.
There is just a tiny problem: While I uploaded pkgbinarymangler,
Gianfranco picked the debhelper reverse idea from my PPA and uploaded
debhelper almost concurrently. So the issue has been fixed twice. :/
I suppose it's better to keep the pkgbinarymangler change, and drop this
extra delta in debhelper compared to Debian. But we can decide that
later, since there is no longer any urgency.
Btw, it cannot be ruled out that the debhelper commit became problematic
to dh_translations by mistake. But I think it's rather related to the
pipes in the failing dh_translations commands.
** Tags removed: block-proposed
** Changed in: debhelper (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: gnome-control-center (Ubuntu)
Status: Triaged => Invalid
** Changed in: gnome-text-editor (Ubuntu)
Status: Triaged => Invalid
--
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/2002845
Title:
debhelper 13.11.4ubuntu1 broke dh-translations
Status in debhelper package in Ubuntu:
Fix Committed
Status in gnome-control-center package in Ubuntu:
Invalid
Status in gnome-text-editor package in Ubuntu:
Invalid
Status in pkgbinarymangler package in Ubuntu:
Fix Committed
Bug description:
Today's debhelper 13.11.4ubuntu1 merge broke dh-translations.
https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1
gnome-text-editor build log excerpt
---
dh_translations
Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu'
--targets |
jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm
line 518.
dh_translations: error: exec (for cmd: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'") failed: No such file or directory
dh_translations: error: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'" returned exit code 25
Other Info
--
Gunnar identified the bad commit as
https://salsa.debian.org/debian/debhelper/-/commit/62a8608
https://launchpad.net/~gunnarhj/+archive/ubuntu/debhelper/+packages
https://pastebin.ubuntu.com/p/P8qM2sHn9C/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/2002845/+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 2002845] Re: debhelper 13.11.4ubuntu1 broke dh-translations
I uploaded pkgbinarymangler with that change in dh_translations.
** Changed in: pkgbinarymangler (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: pkgbinarymangler (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
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/2002845
Title:
debhelper 13.11.4ubuntu1 broke dh-translations
Status in debhelper package in Ubuntu:
Triaged
Status in gnome-control-center package in Ubuntu:
Triaged
Status in gnome-text-editor package in Ubuntu:
Triaged
Status in pkgbinarymangler package in Ubuntu:
Fix Committed
Bug description:
Today's debhelper 13.11.4ubuntu1 merge broke dh-translations.
https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1
gnome-text-editor build log excerpt
---
dh_translations
Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu'
--targets |
jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm
line 518.
dh_translations: error: exec (for cmd: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'") failed: No such file or directory
dh_translations: error: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'" returned exit code 25
Other Info
--
Gunnar identified the bad commit as
https://salsa.debian.org/debian/debhelper/-/commit/62a8608
https://launchpad.net/~gunnarhj/+archive/ubuntu/debhelper/+packages
https://pastebin.ubuntu.com/p/P8qM2sHn9C/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/2002845/+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 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions
I have same bug with clean install of Ubuntu 22.04.01 LTS. I did a reinstall as I assumed a couple of bugs were caused by kernel updates and other non-standard settings, seems not. Problems were the same on 22.10. This one with pointer becoming laggy after maybe a couple hours and maximized windows appearing behind the dock after coming out of suspend. Using X11 seems to solve both issues but there's some stuff I like about Wayland. HP Laptop - 15s-fq1xxx Intel® Core™ i5-1035G4 CPU Mesa Intel® Iris(R) Plus Graphics (ICL GT1.5) -- 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/1982560 Title: Mouse lag/stutter (missed frames) in Wayland sessions Status in gnome-shell package in Ubuntu: Confirmed Bug description: Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem didn't occur in previous version of ubuntu based on xorg. Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc or when heavy operations are done on it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-13 (50 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982560/+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 2002845] Re: debhelper 13.11.4ubuntu1 broke dh-translations
Another and less intrusive idea to solve the problem for now:
I simply picked the qx_cmd() function in Dh_Lib.pm as it looked like
before the interruptive commit mentioned above, and pasted it into the
dh_translations file (and renamed it to qx_meson_cmd). See attached
diff.
Tested successfully with a couple of packages, including gnome-control-
center.
** Patch added: "dh_translations.diff"
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/2002845/+attachment/5641350/+files/dh_translations.diff
--
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/2002845
Title:
debhelper 13.11.4ubuntu1 broke dh-translations
Status in debhelper package in Ubuntu:
Triaged
Status in gnome-control-center package in Ubuntu:
Triaged
Status in gnome-text-editor package in Ubuntu:
Triaged
Status in pkgbinarymangler package in Ubuntu:
Triaged
Bug description:
Today's debhelper 13.11.4ubuntu1 merge broke dh-translations.
https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1
gnome-text-editor build log excerpt
---
dh_translations
Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu'
--targets |
jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm
line 518.
dh_translations: error: exec (for cmd: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'") failed: No such file or directory
dh_translations: error: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'" returned exit code 25
Other Info
--
Gunnar identified the bad commit as
https://salsa.debian.org/debian/debhelper/-/commit/62a8608
https://launchpad.net/~gunnarhj/+archive/ubuntu/debhelper/+packages
https://pastebin.ubuntu.com/p/P8qM2sHn9C/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/2002845/+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
