[Desktop-packages] [Bug 2025520] Re: User fonts are not detected (only system wide fonts)
** Tags added: lunar -- 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/2025520 Title: User fonts are not detected (only system wide fonts) Status in libreoffice package in Ubuntu: New Bug description: Hello, I'm running Kubuntu 23.04. I've installed few fonts from the Settings (Font Manager) and noticed that Libreoffice (snap) can see the system-wide installed fonts, but it doesn't detect the user fonts. I think it should be able to see and works also with the fonts installed for a specific user and not only with the system fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2025520/+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 2025520] [NEW] User fonts are not detected (only system wide fonts)
Public bug reported: Hello, I'm running Kubuntu 23.04. I've installed few fonts from the Settings (Font Manager) and noticed that Libreoffice (snap) can see the system-wide installed fonts, but it doesn't detect the user fonts. I think it should be able to see and works also with the fonts installed for a specific user and not only with the system fonts ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: kubuntu snap -- 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/2025520 Title: User fonts are not detected (only system wide fonts) Status in libreoffice package in Ubuntu: New Bug description: Hello, I'm running Kubuntu 23.04. I've installed few fonts from the Settings (Font Manager) and noticed that Libreoffice (snap) can see the system-wide installed fonts, but it doesn't detect the user fonts. I think it should be able to see and works also with the fonts installed for a specific user and not only with the system fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2025520/+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 1428121]
Another instance in the wild: https://www.reddit.com/r/debian/comments/14lje8f/comment/jpwmckm/?context=3 -- 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/1428121 Title: Intel HDMI Audio not working with IOMMU enabled Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an Nvidia GTX 650. Host uses Intel IGD for video and HDMI audio out. When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on' HDMI audio no longer functions although the device and modules seem to load and I cannot locate any error messages. In this configuration IOMMU functions as expected and I can successfully pass the Nvidia card through to a KVM guest using VFIO. As per this (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug report and the linked bugzilla thread I attempted to use kernel flag 'intel_iommu=on,igfx_off'. This resolves the HDMI audio out but breaks IOMMU as in VGA pass through generates DMA errors. I'm running from a clean installation of 14.10 with no modifications to the kernel or kvm, qemu, libvirt or virt-manager. In either scenario above the analogue audio out continues to function, I haven't tested the optical out as I have no hardware to do so. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-31-generic 3.16.0-31.41 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kelvin 3468 F pulseaudio /dev/snd/controlC3: kelvin 3468 F pulseaudio /dev/snd/controlC0: kelvin 3468 F pulseaudio /dev/snd/controlC1: kelvin 3468 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 4 12:53:17 2015 HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931 InstallationDate: Installed on 2015-02-26 (5 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.16.0-31-generic N/A linux-backports-modules-3.16.0-31-generic N/A linux-firmware 1.138.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1428121/+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 1428121]
Sound pause and resume lags few seconds behind the video, adding solves this problem intel_iommu=on,igfx_off on Intel(R) Celeron(R) 2955U -- 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/1428121 Title: Intel HDMI Audio not working with IOMMU enabled Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an Nvidia GTX 650. Host uses Intel IGD for video and HDMI audio out. When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on' HDMI audio no longer functions although the device and modules seem to load and I cannot locate any error messages. In this configuration IOMMU functions as expected and I can successfully pass the Nvidia card through to a KVM guest using VFIO. As per this (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug report and the linked bugzilla thread I attempted to use kernel flag 'intel_iommu=on,igfx_off'. This resolves the HDMI audio out but breaks IOMMU as in VGA pass through generates DMA errors. I'm running from a clean installation of 14.10 with no modifications to the kernel or kvm, qemu, libvirt or virt-manager. In either scenario above the analogue audio out continues to function, I haven't tested the optical out as I have no hardware to do so. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-31-generic 3.16.0-31.41 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kelvin 3468 F pulseaudio /dev/snd/controlC3: kelvin 3468 F pulseaudio /dev/snd/controlC0: kelvin 3468 F pulseaudio /dev/snd/controlC1: kelvin 3468 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 4 12:53:17 2015 HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931 InstallationDate: Installed on 2015-02-26 (5 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.16.0-31-generic N/A linux-backports-modules-3.16.0-31-generic N/A linux-firmware 1.138.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1428121/+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 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
** Changed in: webkit2gtk (Debian) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in Webkit: Confirmed Status in webkit2gtk package in Ubuntu: Incomplete Status in webkit2gtk package in Debian: Confirmed Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2
[Desktop-packages] [Bug 1988438] Re: Xorg crashes with [Failed to compile FS: 0:1(10): error: GLSL 1.30 is not supported ...] on Intel Penryn/Clarkdale
** Changed in: xorg-server
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1988438
Title:
Xorg crashes with [Failed to compile FS: 0:1(10): error: GLSL 1.30 is
not supported ...] on Intel Penryn/Clarkdale
Status in X.Org X server:
New
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
Crashes X11 back to login screen typically when running the browser.
I refurbish old laptops, and this older HP Pavilion dvb Core Duo with
Intel graphics is probably no longer supported by Mesa 22 from the
searching of the core problems that I did.
Please consider some option for those of us that want to prevent these
older but like-new machines from ending up in a landfill. We still
want a modern up to date secure Gnome2 experience from Ubuntu.
$ grep -nrw error /var/log/Xorg.0.log.old
12: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
483:[ 6900.077] Failed to compile FS: 0:1(10): error: GLSL 1.30 is not
supported. Supported versions are: 1.10, 1.20, and 1.00 ES
518:Fatal server error:
528:[ 6900.148] (EE) Server terminated with error (1). Closing log file.
I tried to use crocus to by adding the MESA invocation to the .profile
but that didn't change the random crashes during Firefox or Chrome
browsing.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5json:
{
"result": "skip"
}
CompositorRunning: None
CurrentDesktop: MATE
Date: Thu Sep 1 08:21:55 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated
Graphics Controller [103c:3627]
Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated
Graphics Controller [103c:3627]
InstallationDate: Installed on 2022-08-15 (16 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic
root=UUID=913d711b-e1de-44cf-9ef1-fd32a54a7815 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2009
dmi.bios.release: 15.49
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.31
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3627
dmi.board.vendor: Quanta
dmi.board.version: 18.42
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.ec.firmware.release: 24.66
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.31:bd08/21/2009:br15.49:efr24.66:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnQuanta:rn3627:rvr18.42:cvnQuanta:ct10:cvrN/A:skuVM222UA#ABA:
dmi.product.family: 103C_5335KV
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.sku: VM222UA#ABA
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1988438/+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 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
FWIW I installed the new version and I confirm that Nautilus search seems snappier. Thanks to you and to the maintainer for your work! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in ibus: New Status in ibus package in Ubuntu: Confirmed Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
The autopkgtest passed for apparmor lunar libreoffice/armhf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Committed Status in evince source package in Jammy: In Progress Status in apparmor source package in Lunar: Fix Committed Status in evince source package in Lunar: Fix Committed Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
The IBus maintainer Takao Fujiwara has submitted a pull request which is intended to address this issue. I applied the pull request and uploaded IBus (for 23.04 and 23.10) to this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus Can users who are affected by the issue please install ibus from my PPA and let us know — either here or at the upstream issue https://github.com/ibus/ibus/issues/2486 — if it improves things. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in ibus: New Status in ibus package in Ubuntu: Confirmed Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
I'm running mesa 22.2.5-0ubuntu0.1~22.04.3 since it was released without any issues any more. Previously, I had between one and a dozend kwin crashes a day, so for me it's definitely fixed in this version. @autra: Do you really see the "kwin_x11: The X11 connection broke: I/O error (code 1)" kwin quits (technically, it's not even a crash as I understand), or maybe something differently which causes kwin to suddenly disappear? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2025476] [NEW] glibtop_get_fsusage() read/write stats not working on encrypted partition
Public bug reported: Ubuntu release: jammy Package version: libgtop-2.0-11 2.40.0-2build3 Kernel version: 5.15.0-76-generic Situation: An encrypted partition (root in this case) is mounted on /dev/mapper/cryptroot . /dev/mapper/cryptroot is actually a symlink to ../dm-0 , i.e. /dev/dm-0 . Expected behaviour: glibtop_get_fsusage(, "/") should return correct read/write statistics for the partition (i.e. fsusage.read and fusage.write). Observed behaviour: fsusage.read and fusage.write are incorrectly returned as zero. I have tried to further track down the problem. linux_2_6_0() in sysdeps/linux/fsusage.c calls get_device() which checks the table of mounted filesystems and returns "mapper/cryptroot", referring to /dev/mapper/cryptroot . get_sys_path() then turns this into the incorrect sys file path "/sys/block/mapper/cryptroot/stat". It should be "/sys/block/dm-0/stat". Proposed solution: get_sys_path() should check if the device file is a symlink and if so, dereference it before using it as a device name. ** Affects: libgtop2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgtop2 in Ubuntu. https://bugs.launchpad.net/bugs/2025476 Title: glibtop_get_fsusage() read/write stats not working on encrypted partition Status in libgtop2 package in Ubuntu: New Bug description: Ubuntu release: jammy Package version: libgtop-2.0-11 2.40.0-2build3 Kernel version: 5.15.0-76-generic Situation: An encrypted partition (root in this case) is mounted on /dev/mapper/cryptroot . /dev/mapper/cryptroot is actually a symlink to ../dm-0 , i.e. /dev/dm-0 . Expected behaviour: glibtop_get_fsusage(, "/") should return correct read/write statistics for the partition (i.e. fsusage.read and fusage.write). Observed behaviour: fsusage.read and fusage.write are incorrectly returned as zero. I have tried to further track down the problem. linux_2_6_0() in sysdeps/linux/fsusage.c calls get_device() which checks the table of mounted filesystems and returns "mapper/cryptroot", referring to /dev/mapper/cryptroot . get_sys_path() then turns this into the incorrect sys file path "/sys/block/mapper/cryptroot/stat". It should be "/sys/block/dm-0/stat". Proposed solution: get_sys_path() should check if the device file is a symlink and if so, dereference it before using it as a device name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgtop2/+bug/2025476/+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 2022369] Re: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th
Tested the 23.04 Wayland session and can confirm that it is better! Feel free to close the bug as this will be fixed with updates / future releases. Thanks for the professional bug handling. -- 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/2022369 Title: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th Status in libinput: Fix Released Status in libinput package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I have an X1 carbon 9th gen with a 4k screen where I use 200% scaling. Unfortunately, the touchpad feels laggy and imprecise when trying to hit click targets. Switching to X11 helps as well as the flat acceleration profile in gnome tweaks. I feel like this is related to how gnome or libinput upscale mouse movement. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 16:57:16 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-15 (18 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/2022369/+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 2023442] Re: totem playback hangs after seeking
** Changed in: gstreamer1.0 Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023442 Title: totem playback hangs after seeking Status in Gstreamer1.0: New Status in gstreamer1.0 package in Ubuntu: Triaged Bug description: Playback hangs after seeking forward and backwards a number of times, with some video files. This can been reproduced in Totem and gst-play-1.0. It seems to be caused by some audio stack related change in Ubuntu 22.04. This does not happen when using the Totem flatpak. upstream bug: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1477 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/2023442/+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 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
** Description changed: - In Amazon Workspaces running Ubuntu 22.04, when attempting to change the - Scale in the Gnome Display settings, if you click on a different scale - (i.e. changing from 100% to 200%) and hitting apply, it will bring up a - prompt asking if you want to keep or revert the changes and there will - be a timer of 20 seconds. If you try to revert the changes (either by - letting the timer expire or by clicking the "revert" button), we will - hit one of the following two behaviors: + [ Impact ] + + When running on the Xdcv X11 server, changing the display scale in + Settings and then clicking 'Revert Settings' instead of 'Keep Changes' + does not revert the settings. + + [ Test Plan ] + + Very complicated; see comment #8. + + [ Where problems could occur ] + + In the list of available graphics modes in Xorg sessions on jammy only + (an equivalent fix already exists in later Ubuntu releases). + + [ Original Description ] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' - When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Jammy fix proposed in: https://salsa.debian.org/gnome-team/mutter/-/merge_requests/98 -- 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/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Kinetic: Fix Released Status in mutter source package in Lunar: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] When running GNOME on the Xdcv X11 server, changing the display scale in Settings and then clicking 'Revert Settings' instead of 'Keep Changes' does not revert the settings. [ Test Plan ] Very complicated; see comment #8. [ Where problems could occur ] In the list of available graphics modes in Xorg sessions on jammy only (an equivalent fix already exists in later Ubuntu releases). [ Original Description ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
We only just noticed a similar fix was upstreamed already in mutter 43.0: https://gitlab.gnome.org/GNOME/mutter/-/commit/16af2e407b49cd4464935a6f9b4efdc32f1339e5 ** Also affects: mutter (Ubuntu Mantic) Importance: Undecided Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Also affects: mutter (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: mutter (Ubuntu Jammy) Status: New => In Progress ** Changed in: mutter (Ubuntu Lunar) Status: New => Fix Released ** Changed in: mutter (Ubuntu Mantic) Status: In Progress => Fix Released ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Mantic) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- 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/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Kinetic: Fix Released Status in mutter source package in Lunar: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown
[Desktop-packages] [Bug 2025299] Re: Firefox 115.0+build1-0ubuntu0.18.04.1~mt1 - Unity Global Menu Missing
The ppa packages are not supported by Ubuntu so closing but that will be fixed before we issue official updates ** Changed in: firefox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2025299 Title: Firefox 115.0+build1-0ubuntu0.18.04.1~mt1 - Unity Global Menu Missing Status in firefox package in Ubuntu: Invalid Bug description: Please accept my apologies if this is the incorrect place to submit this bug. Using Ubuntu 18.04 ESR (Unity Desktop). Upon upgrade from Firefox 114 to 115 noticed that the Unity Global Menu no longer works. Rolling back the package to 114 and installing 102.12 ESR global menu works as expected. This is the package that is on the mozillateam PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2025299/+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 2012734] Re: no audio after update
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2012734 Title: no audio after update Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.10 Release: 22.10 during normal patching Ubuntu pushed from kernel 5.19.0-31 to 5.19.0-35. After this push, I lost audio from my AMD RX570 hdmi. I booted back to -31 waiting for the next kernel push in the hopes the problem would be caught and addressed. It wasn't, and still persists in -38. The card info is below and was taken while booted into -38. 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef) 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] root@x:~# hwinfo --sound 35: PCI 100.1: 0403 Audio device [Created at pci.386] Unique ID: NXNs.TsyFmhFLPLA Parent ID: mnDB.fA+tdbAkMSD SysFS ID: /devices/pci:00/:00:01.1/:01:00.1 SysFS BusID: :01:00.1 Hardware Class: sound Model: "ATI Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0xaaf0 "Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]" SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd" SubDevice: pci 0xaaf0 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xfcf6-0xfcf63fff (rw,non-prefetchable) IRQ: 86 (5 events) Module Alias: "pci:v1002dAAF0sv1458sdAAF0bc04sc0 3i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #31 (PCI bridge) The errors I am getting during intialization are: [ 4.895282] hdaudio hdaudioC0D0: no AFG or MFG node found [ 4.895306] snd_hda_intel :01:00.1: no codecs initialized and if I try to validate the card root@x:~# aplay -l aplay: device_list:274: no soundcards found... I have tried passing numerous arguments to the module but to no avail. Booting back to -31 brings the card right back to fully functioning. I believe there has been an update to snd_hda_intel which is causing this issue and is most likely a regression situation. Can anyone assist? I have searched for a model to be passed specific to AMD cards, but can't find one. Any suggestions would be greatly appreciated. Additionally, I'm wondering if this should be directed to Ubuntu, or should it go to kernel.org the HD-Audio group? Again, thanks for your thoughts. options snd_hda_intel dmic_detect=0 options snd_hda_intel model=generic options snd_hda_intel model=auto options snd_hda_intel probe_mask=1 options snd-intel-dspcfg dsp_driver=1 Under -31 the error messages are not displayed, sound works. If I again validate, I get the below: root@media2:~# aplay -l List of PLAYBACK Hardware Devices card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [65Q825] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pulseaudio 1:16.1+dfsg1-1ubuntu3.1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:gdm1585 F pipewire CasperMD5CheckResult: unknown Date: Fri Mar 24 07:45:50 2023 InstallationDate: Installed on 2019-05-09 (1415 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to kinetic on 2023-01-13 (69 days ago) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS PRO WIFI-CF
[Desktop-packages] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
i've been running previous version 22.2.5-0ubuntu0.1~22.04.2 for a month straight and saw no issues. has the bug been reintroduced in 22.2.5-0ubuntu0.1~22.04.3 ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 878118] Re: please merge po files to upstream? source
The translations are updated now https://git.launchpad.net/software-properties/commit/?id=81efc82 ** Changed in: software-properties Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/878118 Title: please merge po files to upstream? source Status in Software Properties: Fix Released Status in software-properties package in Ubuntu: Invalid Status in software-properties package in Debian: New Bug description: I found software-properties in Rosetta is updated for translations but bzr(lp:ubuntu/software-properties, lp:ubuntu/oneiric/software- properties) and package source (https://launchpad.net/ubuntu/+archive/primary/+files/software- properties_0.81.13.dsc and https://translations.launchpad.net/software-properties) are not. Only https://translations.launchpad.net/ubuntu/oneiric/+source/software- properties/+pots/software-properties is to get newest translation... it's too complicated way. Debian tracks software-properties tarball version, however, it doesn't contain any updated po files. Please merge those and put it to tarball. To manage notifications about this bug go to: https://bugs.launchpad.net/software-properties/+bug/878118/+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 2023442] Re: totem playback hangs after seeking
** Changed in: gstreamer1.0 (Ubuntu) Importance: Undecided => High ** Changed in: gstreamer1.0 (Ubuntu) Status: Confirmed => Triaged ** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #1477 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1477 ** Also affects: gstreamer1.0 via https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1477 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023442 Title: totem playback hangs after seeking Status in Gstreamer1.0: Unknown Status in gstreamer1.0 package in Ubuntu: Triaged Bug description: Playback hangs after seeking forward and backwards a number of times, with some video files. This can been reproduced in Totem and gst-play-1.0. It seems to be caused by some audio stack related change in Ubuntu 22.04. This does not happen when using the Totem flatpak. upstream bug: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1477 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/2023442/+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 2025460] [NEW] night light stopped working
Public bug reported: Same as #1752680 but happening from cold boot and won't work again after disabling/re-enabling night light. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-76.83~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 30 10:25:21 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-24 (978 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/2025460 Title: night light stopped working Status in gnome-shell package in Ubuntu: New Bug description: Same as #1752680 but happening from cold boot and won't work again after disabling/re-enabling night light. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-76.83~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 30 10:25:21 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-24 (978 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2025460/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
Still reproducing on mesa 22.2.5-0ubuntu0.1~22.04.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 878118] Re: please merge po files to upstream? source
It's not an issue for the Ubuntu package since we use language packs ** Also affects: software-properties Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu) Status: New => Invalid ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/878118 Title: please merge po files to upstream? source Status in Software Properties: New Status in software-properties package in Ubuntu: Invalid Status in software-properties package in Debian: New Bug description: I found software-properties in Rosetta is updated for translations but bzr(lp:ubuntu/software-properties, lp:ubuntu/oneiric/software- properties) and package source (https://launchpad.net/ubuntu/+archive/primary/+files/software- properties_0.81.13.dsc and https://translations.launchpad.net/software-properties) are not. Only https://translations.launchpad.net/ubuntu/oneiric/+source/software- properties/+pots/software-properties is to get newest translation... it's too complicated way. Debian tracks software-properties tarball version, however, it doesn't contain any updated po files. Please merge those and put it to tarball. To manage notifications about this bug go to: https://bugs.launchpad.net/software-properties/+bug/878118/+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 2020272] Re: [MIR] libsigc++-3.0
** Package changed: ubuntu => libsigc++-3.0 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsigc++-3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020272 Title: [MIR] libsigc++-3.0 Status in libsigc++-3.0 package in Ubuntu: Fix Released Bug description: [Availability] The package libsigc++-3.0 is already in Ubuntu universe. The package libsigc++-3.0 is built for all Ubuntu architectures except i386 (where it is not needed) Link to package https://launchpad.net/ubuntu/+source/libsigc++-3.0 [Rationale] - The package libsigc++-3.0 is a new runtime dependency of package transmission that we already support. (Transmission has been included in Ubuntu Desktop for many years. Transmission previously used C for the desktop app but C++ for much of the rest of the codebase. With the latest version, Transmission has standardized on C++ for all its codebase.) - libsigc++-3.0 is part of the GTK4 stack for C++. A different source package, libsigc++-2.0, is part of the GTK3 C++ stack and is currently in main. For more rationale about promoting the GTK4 stack for C++ to main, see the gtkmm4.0 MIR bug LP: #2020472 - The package libsigc++-3.0 is required in Ubuntu main no later than August 17, Ubuntu 23.10 Feature Freeze, because it is a dependency of transmission and perhaps gnome-system-monitor 45. [Security] - No CVEs/security issues in this software in the past + https://ubuntu.com/security/cve?package=libsigc++-2.0 + https://security-tracker.debian.org/tracker/source-package/libsigc++-2.0 + https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libsigc++ - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Package does not open privileged ports (ports < 1024) - Package does not contain extensions to security-sensitive software (filters, scanners, plugins, UI skins, ...) [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs + Ubuntu https://bugs.launchpad.net/ubuntu/+source/libsigc++-2.0 https://bugs.launchpad.net/ubuntu/+source/libsigc++-3.0 + Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libsigc++-2.0 https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libsigc++-3.0 + Upstream https://github.com/libsigcplusplus/libsigcplusplus/issues - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpad.net/ubuntu/+source/libsigc++-3.0/3.4.0-2/+latestbuild/amd64 - The package runs an autopkgtest, and is currently passing on all architectures (except for i386 where it is not built) https://autopkgtest.ubuntu.com/packages/libsigc++-3.0 - The package does have not failing autopkgtests right now [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer field (package is maintained in Debian) - This package does not yield massive lintian Warnings, Errors - Please link to a recent build log of the package https://launchpad.net/ubuntu/+source/libsigc++-3.0/3.4.0-2/+latestbuild/amd64 - Please attach the full output you have got from `lintian --pedantic` as an extra post to this bug. - Lintian overrides are not present - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf questions - Packaging and build is easy https://salsa.debian.org/gnome-team/libsigcplusplus-3.0/-/blob/debian/master/debian/rules [UI standards] - Application is not end-user facing (does not need translation) - Application is not end-user facing (does not need .desktop file) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - Owning Team will be Desktop Packages - Team is not yet, but will subscribe to the package before promotion - This does not use static builds - This does not use vendored code - This package is not rust based - The package has been built in the archive more recently than the last test rebuild [Background information] The Package description explains the package well Upstream Name is libsigc++ or libsigcplusplus (due to name restrictions in things like GitHub) Link to upstream project https://github.com/libsigcplusplus/libsigcplusplus/ To manage notifications about this bug go to:
[Desktop-packages] [Bug 1993359] Re: profile snap-update-ns.firefox is denied
I am experiencing this issue in Ubuntu 22.04.2 LTS. It possibly causes freezes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1993359 Title: profile snap-update-ns.firefox is denied Status in firefox package in Ubuntu: Confirmed Bug description: profile snap-update-ns.firefox is denied on fresh kinetic boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1993359/+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 2017337] Re: [ASUS Zenbook UX303UB] Multi touch broken on lunar (23.04) (xorg + wayland) for Focaltech touchpad
Doesn't matter. Chris has almost the same hardware so let's go with that. ** Package changed: libinput (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => 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/2017337 Title: [ASUS Zenbook UX303UB] Multi touch broken on lunar (23.04) (xorg + wayland) for Focaltech touchpad Status in libinput: New Status in Ubuntu: Fix Released Bug description: Multi touch broken on lunar (23.04) (xorg + wayland) for Focaltech touchpad Since the upgrade of my laptop (ASUS Zenbook UX303UB), multi touch has been acting erraticly in the following situations: - two finger scrolling - one finger clicks left mouse, other finger drags when two fingers are moving onto the surface, the cursor is fleeing to the right/top of the screen. (See attached screencast) The issue happens regardless of xorg/wayland. I enclosed a screencast video that demonstrates the issue. In this scenario, I am moving a window downwards using two methods: - Click and drag with one finger : working - Click the left click area with one finger, and drag using the other : not working, cursor is fleeing - When two fingers are present, and one of them is moving, I am experiencing the "fleeing cursor" issue Workaround : using left edge scrolling works as temporary workaround for scrolling, but click drag using a single finger is really cumbersome. Here is the output of the `xinput` command on Xorg: ``` ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ FocalTechPS/2 FocalTech Touchpadid=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)] ↳ Asus WMI hotkeysid=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` Here is the output of the `xinput` command on wayland: ``` WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ xwayland-pointer:15 id=6[slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:15id=7[slave pointer (2)] ⎜ ↳ xwayland-pointer-gestures:15id=8[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ xwayland-keyboard:15id=9[slave keyboard (3)] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/2017337/+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 2025006] Re: Monitor colour profile not loaded on login in 44.2
I went back and tested lunar on the same machine and there is no bug there even though lunar has 44.2 now. Makes me think this might be a kernel issue since mantic has 6.3 now. ** Tags added: gamma ** Summary changed: - Monitor colour profile not loaded on login in 44.2 + Monitor colour profile not loaded on login ** Description changed: My custom monitor colour profile is showing as installed in Settings, - but is not loaded upon login in 44.2 + but is not loaded upon login (on mantic only). Workaround: Ctrl+Alt+F3, Ctrl+Alt+F2, solved. The colour profile is now applied. -- 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/2025006 Title: Monitor colour profile not loaded on login Status in mutter package in Ubuntu: New Bug description: My custom monitor colour profile is showing as installed in Settings, but is not loaded upon login (on mantic only). Workaround: Ctrl+Alt+F3, Ctrl+Alt+F2, solved. The colour profile is now applied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2025006/+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 2025320] Re: [nvidia] External display sometimes frozen, after logout/login has only black screen.
Thanks, I'll take this into account :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2025320 Title: [nvidia] External display sometimes frozen, after logout/login has only black screen. Status in nvidia-graphics-drivers-530 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: After some system updates my external screen is not working properly. After logout/log in it keeps black or with a background image and is frozen. Moreover, it happens from time to time even when you were logged in without any explanation. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-530 530.41.03-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 29 09:06:10 2023 InstallationDate: Installed on 2023-02-19 (129 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2025320/+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
