[Desktop-packages] [Bug 1979127] [NEW] Ethernet icon is disabled even when internet is working
Public bug reported: This has happened for the last 2 weeks. Even if the internet is working, the ethernet icon in app indicator changes to a no-internet icon. I don't know what the issue is. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-51-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 19 09:25:22 2022 InstallationDate: Installed on 2021-08-21 (301 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1979127 Title: Ethernet icon is disabled even when internet is working Status in network-manager package in Ubuntu: New Bug description: This has happened for the last 2 weeks. Even if the internet is working, the ethernet icon in app indicator changes to a no-internet icon. I don't know what the issue is. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-51-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 19 09:25:22 2022 InstallationDate: Installed on 2021-08-21 (301 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1979127/+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 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)
Crashed on login. I tried to login once. Nothing happened. Then again. I have a hybrid Intel+Nvidia laptop. I also heard sounds coming from my laptops speakers and they should come from my HDMI audio device usually (I haven't noticed that before). If that's an indication. After the login the sounds started coming out the the HDMI device. I have set my external HDMI monitor as the primary monitor and the only one enabled due to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040 I haven't enabled the workaround described above: `Just add MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment and then reboot.` While not related to this crash: it would be great if the login screen appears on the primary device, which in my case is the external HDMI one. The login currently appears on the internal display. -- 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/1959507 Title: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I'm starting a VM Ubuntu 22.04 on QEMU/KVM and this alert appears. It seems to myself there is an issue between Wayland and spice-vdagent. Regards, Michel ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 29 09:52:12 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-01-28 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 41.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) at pthread_kill.c:44 __pthread_kill_internal (signo=6, threadid=140083783699840) at pthread_kill.c:80 __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at pthread_kill.c:91 __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 __GI_abort () at abort.c:79 Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+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 1979126] [NEW] [22V280-L.BY31P1, Realtek ALC256, Speaker, Internal] No sound at all
Public bug reported: Som desaparece e não consigo escutar audios de youtube ou outros ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alberto1041 F pulseaudio /dev/snd/pcmC0D0c: alberto1041 F...m pulseaudio /dev/snd/pcmC0D0p: alberto1041 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 18 22:28:20 2022 InstallationDate: Installed on 2022-03-22 (89 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alberto1041 F pulseaudio /dev/snd/pcmC0D0c: alberto1041 F...m pulseaudio /dev/snd/pcmC0D0p: alberto1041 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [22V280-L.BY31P1, Realtek ALC256, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 22VC0251 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 22V280 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr22VC0251X64:bd08/01/2018:br0.1:svnLGElectronics:pn22V280-L.BY31P1:pvr0.1:rvnLGElectronics:rn22V280:rvrFAB1:cvnLGElectronics:ct13:cvr0.1:sku: dmi.product.family: V Series dmi.product.name: 22V280-L.BY31P1 dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1979126 Title: [22V280-L.BY31P1, Realtek ALC256, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Som desaparece e não consigo escutar audios de youtube ou outros ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alberto1041 F pulseaudio /dev/snd/pcmC0D0c: alberto1041 F...m pulseaudio /dev/snd/pcmC0D0p: alberto1041 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 18 22:28:20 2022 InstallationDate: Installed on 2022-03-22 (89 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alberto1041 F pulseaudio /dev/snd/pcmC0D0c: alberto1041 F...m pulseaudio /dev/snd/pcmC0D0p: alberto1041 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [22V280-L.BY31P1, Realtek ALC256, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 22VC0251 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 22V280 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr22VC0251X64:bd08/01/2018:br0.1:svnLGElectronics:pn22V280-L.BY31P1:pvr0.1:rvnLGElectronics:rn22V280:rvrFAB1:cvnLGElectronics:ct13:cvr0.1:sku: dmi.product.family: V Series dmi.product.name: 22V280-L.BY31P1 dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1979126/+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 1979121] [NEW] [MIR] webp-pixbuf-loader
Public bug reported: [Availability] The package webp-pixbuf-loader is already in Ubuntu universe. The package webp-pixbuf-loader build for the architectures it is designed to work on. It currently builds and works for architetcures: amd64 arm64 armhf ppc64el riscv64 s390x(failing) Link to package https://launchpad.net/ubuntu/+source/webp-pixbuf-loader [Rationale] - The package webp-pixbuf-loader is required in Ubuntu main to be able to open webp image from the standard viewer (eog) and get thumbnails in the filemanage - The package webp-pixbuf-loader will generally be useful for a large part of our user base - The package webp-pixbuf-loader is required in Ubuntu main no later than aug 25 due to feature freeze [Security] - No CVEs/security issues in this software in the past - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is new in Debian/Ubuntu and has currently no bug reported - 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://launchpadlibrarian.net/607631911/buildlog_ubuntu-kinetic-amd64.webp-pixbuf-loader_0.0.5-2_BUILDING.txt.gz - The package does not run an autopkgtest because image loaders aren't easy to verify in that setup, but we will open example webp files as a manual testcase before doing package updates. [Quality assurance - packaging] - debian/watch is present and works - the package is in sync with Debian and has a valid maintainer definition - The package displays no lintian warnings - Please link to a recent build log of the package https://launchpadlibrarian.net/607631911/buildlog_ubuntu-kinetic-amd64.webp-pixbuf-loader_0.0.5-2_BUILDING.txt.gz - Lintian overrides are not present [Maintenance/Owner] - Owning Team will be desktop-packages - Team is already subscribed to the package - This does not use static builds - This does not use vendored code - 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 webp-pixbuf-loader Link to upstream project https://github.com/aruiz/webp-pixbuf-loader/ ** Affects: webp-pixbuf-loader (Ubuntu) Importance: Low Status: New ** Description changed: [Availability] The package webp-pixbuf-loader is already in Ubuntu universe. The package webp-pixbuf-loader build for the architectures it is designed to work on. It currently builds and works for architetcures: amd64 arm64 armhf ppc64el riscv64 s390x(failing) Link to package https://launchpad.net/ubuntu/+source/webp-pixbuf-loader [Rationale] - The package webp-pixbuf-loader is required in Ubuntu main to be able to open webp image from the standard viewer (eog) and get thumbnails in the filemanage - The package webp-pixbuf-loader will generally be useful for a large part of our user base - TODO-A: - The package webp-pixbuf-loader is required in Ubuntu main no - later than aug 25 due to feature freeze + - The package webp-pixbuf-loader is required in Ubuntu main no later + than aug 25 due to feature freeze [Security] - No CVEs/security issues in this software in the past - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is new in Debian/Ubuntu and has currently no bug reported - 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://launchpadlibrarian.net/607631911/buildlog_ubuntu-kinetic-amd64.webp-pixbuf-loader_0.0.5-2_BUILDING.txt.gz + it makes the build fail, link to build log https://launchpadlibrarian.net/607631911/buildlog_ubuntu-kinetic-amd64.webp-pixbuf-loader_0.0.5-2_BUILDING.txt.gz - The package does not run an autopkgtest because image loaders aren't easy to verify in that setup, but we will open example webp files as a manual testcase before doing package updates. [Quality assurance - packaging] - debian/watch is present and works - the package is in sync with Debian and has a valid maintainer definition - The package displays no lintian warnings - Please link to a recent build log of the package
[Desktop-packages] [Bug 1978547] Re: nautilus crash on search
The screenshot is the same file as the non-ascii one. About photo: After two letters searched, it stops responding (as is shown on the screenshot) and it poped up a message says "Force quit" or "Wait" (I am not sure how it truly is in English, I translate it) ** Attachment added: "screenshot.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978547/+attachment/5598146/+files/screenshot.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/1978547 Title: nautilus crash on search Status in nautilus package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 LTS (updated from 21.10) nautilus 1.42.1.1-0ubuntu 15.15.0-37-generic flatpak installed Type=x11 Expected to happen: 1. open nautilus 2. type anything in search box in any folder (remote or not, empty or not) 3. nautilus do the search. What happens: 1. open nautilus 2. type anything in search box in any folder (remote or not, empty or not) 3. nautilus crashes and prompt to end the process What I've tested: 1. sudo apt install --reinstall nautilus 2. rm ~/.config/nautilus none worked Strange result: sometimes (same search, same folder) it doesn't crash. After waiting about 1min (!) doing nothing, the search results appear. After this happy long time, if I try other searches without closing the window, they work as expected. I would have posted this a week earlier, but then the strange result first came out. So I thought that I could figure it out, but I couldn't. Before that I didn't realize how important the search box was. Now I have installed nemo as I was waiting nautilus to be fixed. If I could test anything that it could help, I would love to help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978547/+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 1979118] [NEW] gnome-shell crashed with SIGSEGV in __GI_getenv()
Public bug reported: Just started, only firefox-trunk active ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-shell 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.21.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Jun 18 15:41:24 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-05-14 (34 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220512) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 42.2-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7f6ea4325c1d <__GI_getenv+173>:cmp (%r12),%bp PC (0x7f6ea4325c1d) ok source "(%r12)" (0xfca16778d75cc123) not located in a known VMA region (needed readable region)! destination "%bp" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_getenv (name=0x7f6ea355531e "NTCONFIG_SYSROOT") at ./stdlib/getenv.c:84 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 FcConfigBuildFonts () from /lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash kinetic need-amd64-retrace ** Information type changed from Private to Public -- 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/1979118 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() Status in gnome-shell package in Ubuntu: New Bug description: Just started, only firefox-trunk active ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-shell 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.21.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Jun 18 15:41:24 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-05-14 (34 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220512) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 42.2-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7f6ea4325c1d <__GI_getenv+173>: cmp (%r12),%bp PC (0x7f6ea4325c1d) ok source "(%r12)" (0xfca16778d75cc123) not located in a known VMA region (needed readable region)! destination "%bp" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_getenv (name=0x7f6ea355531e "NTCONFIG_SYSROOT") at ./stdlib/getenv.c:84 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 FcConfigBuildFonts () from /lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1979118/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
Sure enough I hit the problem with LANGUAGE=en_US transmission-gtk http://file- st06.karelia.ru/7nqk5q/9b587eaf2d8bdc4c751ca979bbb321aa/a186e8a2a0f5d8d1249ad69c8a6648f4/1.png I've noticed that the labels change to this mess in a fraction of a second after the widgets are drawn. And there are thousands of error messages like above that are spammed into .xsession-errors -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979116] [NEW] no USB-key any more in the sidebar of the save-dialog
Public bug reported: If I want to save a new document, then in the save-dialog there's no USB-key any more in the sidebar (so, on the left side), no matter if in the Options (in "LibreOffice" in "General") "Use LibreOffice dialogs" is checked or unchecked. But the USB-key still appears in the file-manager of the system. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.13.0-44.49-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Jun 18 12:05:53 2022 InstallationDate: Installed on 2022-02-06 (131 days ago) InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1979116 Title: no USB-key any more in the sidebar of the save-dialog Status in libreoffice package in Ubuntu: New Bug description: If I want to save a new document, then in the save-dialog there's no USB-key any more in the sidebar (so, on the left side), no matter if in the Options (in "LibreOffice" in "General") "Use LibreOffice dialogs" is checked or unchecked. But the USB-key still appears in the file-manager of the system. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.13.0-44.49-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Jun 18 12:05:53 2022 InstallationDate: Installed on 2022-02-06 (131 days ago) InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1979116/+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 1979111] Re: Changing printer default still printers to previous default in browser
It's a guess the issue is the browser or cups not picking up the new default printer right away. ** Package changed: ubuntu => chromium-browser (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1979111 Title: Changing printer default still printers to previous default in browser Status in chromium-browser package in Ubuntu: New Bug description: Ubuntu Desktop 20.04, fully updated. Budgie Desktop Pre-configured printer profiles with predefined settings so we get the exact profiles we need. Settings have not changed in well over a year. Noticed in the past few months that when a USB printer is swapped with a slightly different model but same manufacture we do the following. 1. Update the device URI. Save. Test print which works. 2. Set default printer to the new printer. 3. In a chromium browser that has kiosk mode enabled for auto print. Attempt to print which prints to the previous defaulted printer. If that happens, we delete the previous defaulted printer profile and print again from the browser and it works. The entire time the browser hasn't been closed or refreshed. Run the command to add the previous default printer. Browser prints to the current default printer. Never restarted cups service between step 2 or 3. This has happened twice now on two different machines with the exact same software/configuration, possibly different printer models selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1979111/+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 1979113] [NEW] Kinetic sound disappeared after today updates
Public bug reported: on my laptop sound disappeared after today updates. Sound was already disappeared on my two desktop but I didn't know which updates to attribute the problem to. Today updates are: Start-Date: 2022-06-18 10:05:42 Commandline: apt upgrade Requested-By: corrado (1000) Upgrade: gnome-text-editor:amd64 (42.1-1, 42.2-1), tracker:amd64 (3.3.1-1, 3.3.1-2), libedata-book-1.2-26:amd64 (3.44.2-1, 3.44.2-2), libkeyutils1:amd64 (1.6.1-2ubuntu3, 1.6.1-3ubuntu1), libebook-1.2-20:amd64 (3.44.2-1, 3.44.2-2), libecal-2.0-1:amd64 (3.44.2-1, 3.44.2-2), libedataserver-1.2-26:amd64 (3.44.2-1, 3.44.2-2), evolution-data-server:amd64 (3.44.2-1, 3.44.2-2), libsnmp-base:amd64 (5.9.1+dfsg-1ubuntu2.1, 5.9.1+dfsg-4ubuntu1), libqt5serialport5:amd64 (5.15.4-1, 5.15.4-2), libxrender1:amd64 (1:0.9.10-1build4, 1:0.9.10-1.1), libsnmp40:amd64 (5.9.1+dfsg-1ubuntu2.1, 5.9.1+dfsg-4ubuntu1), evolution-data-server-common:amd64 (3.44.2-1, 3.44.2-2), pipewire-media-session:amd64 (0.4.1-2ubuntu2, 0.4.1-3ubuntu1), libglib2.0-bin:amd64 (2.72.1-1, 2.72.2-2), libqt5positioning5:amd64 (5.15.4+dfsg-1, 5.15.4+dfsg-2), libpipewire-0.3-common:amd64 (0.3.51-1ubuntu3, 0.3.52-1), pipewire-pulse:amd64 (0.3.51-1ubuntu3, 0.3.52-1), gnome-bluetooth-3-common:amd64 (42.0-5, 42.1-1), libqt5core5a:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), qt5-gtk-platformtheme:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), libgspell-1-common:amd64 (1.10.0-1, 1.11.1-1), libgtksourceview-5-common:amd64 (5.4.1-3build1, 5.4.2-1), libmalcontent-0-0:amd64 (0.10.4-1, 0.10.5-1), libqt5charts5:amd64 (5.15.4-1, 5.15.4-2), libqt5script5:amd64 (5.15.4+dfsg-1, 5.15.4+dfsg-2), libencode-locale-perl:amd64 (1.05-1.1, 1.05-2), libqt5network5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), tracker-miner-fs:amd64 (3.3.0-1build1, 3.3.1-1), libgspell-1-2:amd64 (1.10.0-1, 1.11.1-1), pipewire:amd64 (0.3.51-1ubuntu3, 0.3.52-1), libqt5dbus5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), libsepol2:amd64 (3.4-1, 3.4-2), firefox-trunk:amd64 (103.0~a1~hg20220612r620615-0ubuntu0.22.10.1~umd1, 103.0~a1~hg20220615r620926-0ubuntu0.22.10.1~umd1), gir1.2-gtk-3.0:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libcamel-1.2-63:amd64 (3.44.2-1, 3.44.2-2), libglib2.0-data:amd64 (2.72.1-1, 2.72.2-2), gnome-calendar:amd64 (42.1-1, 42.2-1), libqt5widgets5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), libexempi8:amd64 (2.5.2-1build1, 2.6.1-2), libqt5gui5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), libgstreamer-plugins-good1.0-0:amd64 (1.20.2-1ubuntu2, 1.20.3-1ubuntu1), libgnome-bluetooth-3.0-13:amd64 (42.0-5, 42.1-1), libebook-contacts-1.2-3:amd64 (3.44.2-1, 3.44.2-2), libwoff1:amd64 (1.0.2-1build4, 1.0.2-2), libqt5multimedia5:amd64 (5.15.4-1, 5.15.4-2), libedataserverui-1.2-3:amd64 (3.44.2-1, 3.44.2-2), libxtst6:amd64 (2:1.2.3-1build4, 2:1.2.3-1.1), gir1.2-gnomebluetooth-3.0:amd64 (42.0-5, 42.1-1), libspa-0.2-bluetooth:amd64 (0.3.51-1ubuntu3, 0.3.52-1), gstreamer1.0-gtk3:amd64 (1.20.2-1ubuntu2, 1.20.3-1ubuntu1), ipp-usb:amd64 (0.9.21-1, 0.9.22-1), gstreamer1.0-plugins-good:amd64 (1.20.2-1ubuntu2, 1.20.3-1ubuntu1), libhtml-format-perl:amd64 (2.12-1.1, 2.12-2), libgupnp-av-1.0-3:amd64 (0.14.0-3, 0.14.1-1), gstreamer1.0-pipewire:amd64 (0.3.51-1ubuntu3, 0.3.52-1), enchant-2:amd64 (2.3.2-1ubuntu2, 2.3.3-1), pipewire-bin:amd64 (0.3.51-1ubuntu3, 0.3.52-1), libqt5svg5:amd64 (5.15.4-1, 5.15.4-2), libglibmm-2.4-1v5:amd64 (2.66.2-2, 2.66.4-1), tracker-extract:amd64 (3.3.0-1build1, 3.3.1-1), libgtksourceview-5-0:amd64 (5.4.1-3build1, 5.4.2-1), libqt5multimediawidgets5:amd64 (5.15.4-1, 5.15.4-2), libestr0:amd64 (0.1.10-2.1build3, 0.1.11-1), libglib2.0-0:amd64 (2.72.1-1, 2.72.2-2), libspa-0.2-modules:amd64 (0.3.51-1ubuntu3, 0.3.52-1), gnome-shell-extension-ubuntu-dock:amd64 (72~ubuntu5, 72~ubuntu6), libgtk-3-0:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libgtkmm-3.0-1v5:amd64 (3.24.5-1build1, 3.24.6-1), libopenmpt0:amd64 (0.6.3-1, 0.6.4-1), gtk-update-icon-cache:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libedata-cal-2.0-1:amd64 (3.44.2-1, 3.44.2-2), libgtk-3-common:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libgtk-3-bin:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libtracker-sparql-3.0-0:amd64 (3.3.1-1, 3.3.1-2), libenchant-2-2:amd64 (2.3.2-1ubuntu2, 2.3.3-1), libpipewire-0.3-modules:amd64 (0.3.51-1ubuntu3, 0.3.52-1), inxi:amd64 (3.3.16-1-1, 3.3.18-1-1), libsigc++-2.0-0v5:amd64 (2.10.4-2ubuntu3, 2.10.8-1), python3-paramiko:amd64 (2.9.3-0ubuntu1, 2.10.4-1ubuntu1), libnet-smtp-ssl-perl:amd64 (1.04-1, 1.04-1.1), intel-media-va-driver:amd64 (22.4.2+dfsg1-2, 22.4.3+dfsg1-1), libxv1:amd64 (2:1.0.11-1build2, 2:1.0.11-1.1), libebackend-1.2-10:amd64 (3.44.2-1, 3.44.2-2), libpipewire-0.3-0:amd64 (0.3.51-1ubuntu3, 0.3.52-1) End-Date: 2022-06-18 10:06:01 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire 0.3.52-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.21.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop:
[Desktop-packages] [Bug 1979111] [NEW] Changing printer default still printers to previous default in browser
You have been subscribed to a public bug: Ubuntu Desktop 20.04, fully updated. Budgie Desktop Pre-configured printer profiles with predefined settings so we get the exact profiles we need. Settings have not changed in well over a year. Noticed in the past few months that when a USB printer is swapped with a slightly different model but same manufacture we do the following. 1. Update the device URI. Save. Test print which works. 2. Set default printer to the new printer. 3. In a chromium browser that has kiosk mode enabled for auto print. Attempt to print which prints to the previous defaulted printer. If that happens, we delete the previous defaulted printer profile and print again from the browser and it works. The entire time the browser hasn't been closed or refreshed. Run the command to add the previous default printer. Browser prints to the current default printer. Never restarted cups service between step 2 or 3. This has happened twice now on two different machines with the exact same software/configuration, possibly different printer models selected. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Changing printer default still printers to previous default in browser https://bugs.launchpad.net/bugs/1979111 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. -- 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 1979110] Re: brltty crashed with SIGSEGV in runSpeechDriverThread()
*** This bug is a duplicate of bug 1978521 *** https://bugs.launchpad.net/bugs/1978521 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1978521, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1979110/+attachment/5598091/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1979110/+attachment/5598093/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1979110/+attachment/5598097/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1979110/+attachment/5598098/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1979110/+attachment/5598099/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1979110/+attachment/5598100/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1979110/+attachment/5598101/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1978521 brltty crashed with SIGSEGV in asyncDiscardEvent() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1979110 Title: brltty crashed with SIGSEGV in runSpeechDriverThread() Status in brltty package in Ubuntu: New Bug description: doing nothing, just firefox open ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: brltty 6.4-6ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.21.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Sat Jun 18 08:55:55 2022 ExecutablePath: /usr/bin/brltty InstallationDate: Installed on 2022-05-23 (25 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220512) ProcCmdline: /bin/brltty --no-daemon SegvAnalysis: Segfault happened at: 0x559dcf843e48 :mov 0x20(%rbp),%rdi PC (0x559dcf843e48) ok source "0x20(%rbp)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: brltty StacktraceTop: runSpeechDriverThread () ?? () start_thread (arg=) at ./nptl/pthread_create.c:442 clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Title: brltty crashed with SIGSEGV in runSpeechDriverThread() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1979110/+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 1976204] Re: Screen freeze if a 4K monitor is added to a 4K laptop while DING is active
Good news: I can reproduce the bug now using an HP Skylake laptop with built-in 4K panel. Everything freezes if I add an external 4K display. The freeze does NOT occur if I have DING disabled. If I use both monitors without DING, then only enabling DING makes the freeze happen again. -- 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/1976204 Title: Screen freeze if a 4K monitor is added to a 4K laptop while DING is active Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse don't work during the screen freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-17 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Package: gnome-shell 42.1-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-35-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/oem-priority/+bug/1976204/+subscriptions
