[Bug 2065122] Re: Dual monitor setup not working after sleep/logout
*** This bug is a duplicate of bug 2065081 *** https://bugs.launchpad.net/bugs/2065081 I'm also seeing these error messages which could be more relevant: 2024-06-05T09:19:52.551520+02:00 pc gnome-shell[164087]: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow#012#012Stack trace:#012 _promisify/proto[asyncFunc]/https://bugs.launchpad.net/bugs/2065122 Title: Dual monitor setup not working after sleep/logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2065122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065122] Re: Dual monitor setup not working after sleep/logout
*** This bug is a duplicate of bug 2065081 *** https://bugs.launchpad.net/bugs/2065081 I'm seeing a similar behavior and have no graphic cards on my machine (using the integrated graphics from my AMD CPU). Among other error messages I'm seeing the below: 2024-06-05T09:19:16.960412+02:00 pc gsd-media-keys[73033]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed 2024-06-05T09:19:16.974507+02:00 pc gnome-shell[72857]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed 2024-06-05T09:19:16.974726+02:00 pc gnome-shell[72857]: ** 2024-06-05T09:19:16.974771+02:00 pc gnome-shell[72857]: libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) 2024-06-05T09:19:16.974797+02:00 pc gnome-shell[72857]: Bail out! libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) 2024-06-05T09:19:16.974814+02:00 pc gnome-shell[72857]: GNOME Shell crashed with signal 6 2024-06-05T09:19:16.974844+02:00 pc gnome-shell[72857]: == Stack trace for context 0x577eefdc4b70 == 2024-06-05T09:19:16.974865+02:00 pc gnome-shell[72857]: #0 7ffcb4fe9a80 b file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/tilingWindowManager.js:99 (28d7487d3060 @ 78) 2024-06-05T09:19:16.974891+02:00 pc gnome-shell[72857]: #1 7ffcb4fe9b80 b file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/tilingWindowManager.js:87 (28d7487ccfb0 @ 109) 2024-06-05T09:19:16.974913+02:00 pc gnome-shell[72857]: #2 7ffcb4fe9c90 b self-hosted:241 (67fffb97a60 @ 279) 2024-06-05T09:19:16.974937+02:00 pc gnome-shell[72857]: #3 577eefe87dd0 i file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/tilingWindowManager.js:78 (28d7487ccf60 @ 183) 2024-06-05T09:19:16.974956+02:00 pc gnome-shell[72857]: #4 7ffcb4fea760 b file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/tilingWindowManager.js:566 (28d7487d36a0 @ 208) 2024-06-05T09:19:16.974979+02:00 pc gnome-shell[72857]: #5 577eefe87d00 i file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:408 (28d7487c0650 @ 86) 2024-06-05T09:19:16.975004+02:00 pc gnome-shell[72857]: #6 577eefe87b88 i file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:386 (28d7487c05b0 @ 1703) 2024-06-05T09:19:16.975034+02:00 pc gnome-shell[72857]: #7 577eefe87af8 i resource:///org/gnome/shell/ui/init.js:21 (67fffb70bf0 @ 48) 2024-06-05T09:19:17.143795+02:00 pc /usr/libexec/gdm-x-session[72651]: (II) AMDGPU(0): EDID vendor "LEN", prod id 26079 2024-06-05T09:19:17.143871+02:00 pc /usr/libexec/gdm-x-session[72651]: (II) AMDGPU(0): Using hsync ranges from config file 2024-06-05T09:19:17.143891+02:00 pc /usr/libexec/gdm-x-session[72651]: (II) AMDGPU(0): Using vrefresh ranges from config file 2024-06-05T09:19:17.348839+02:00 pc kernel: usb 3-2.2: reset high-speed USB device number 3 using xhci_hcd 2024-06-05T09:19:17.385825+02:00 pc mattermost-desktop_mattermost-desktop.desktop[73821]: [73821:0605/091917.385501:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed 2024-06-05T09:19:17.387346+02:00 pc mattermost-desktop_mattermost-desktop.desktop[73821]: [73821:0605/091917.387284:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed 2024-06-05T09:19:18.094021+02:00 pc /usr/libexec/gdm-x-session[72651]: (WW) AMDGPU(0): get vblank counter failed: Invalid argument 2024-06-05T09:19:18.094096+02:00 pc /usr/libexec/gdm-x-session[72651]: (WW) AMDGPU(0): get vblank counter failed: Invalid argument 2024-06-05T09:19:18.094246+02:00 pc mattermost-desktop_mattermost-desktop.desktop[73944]: [73944:0605/091918.093966:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! 2024-06-05T09:19:18.095678+02:00 pc /usr/libexec/gdm-x-session[72651]: (WW) AMDGPU(0): get vblank counter failed: Invalid argument 2024-06-05T09:19:18.095887+02:00 pc /usr/libexec/gdm-x-session[72651]: (WW) AMDGPU(0): get vblank counter failed: Invalid argument 2024-06-05T09:19:18.095992+02:00 pc mattermost-desktop_mattermost-desktop.desktop[73944]: [73944:0605/091918.095901:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! 2024-06-05T09:19:18.098129+02:00 pc /usr/libexec/gdm-x-session[72651]: (WW) AMDGPU(0): get vblank counter failed: Invalid argument 2024-06-05T09:19:18.098196+02:00 pc mattermost-desktop_mattermost-desktop.desktop[73944]: [73944:0605/091918.098124:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
[Bug 1996946] Re: Memory leak on every frame when reading GIF animations
** Changed in: gdk-pixbuf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1996946 Title: Memory leak on every frame when reading GIF animations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1996946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971916] Re: error in the system
Hi, thanks for your response there's nothing but a message when I turn on the computer. it says internal error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971916 Title: error in the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1971916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971916] [NEW] error in the system
Public bug reported: I get several messages when I start the UBUNTU OS ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu May 5 21:42:12 2022 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3410/3430] [1002:95c2] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 3410/3430] [103c:30e9] InstallationDate: Installed on 2022-05-02 (3 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Hewlett-Packard HP Compaq 6830s (FR883LA#ABM) ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-142-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZD Ver. F.0F dmi.board.name: 30E9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 95.1D dmi.chassis.asset.tag: CNU8504GHF dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZDVer.F.0F:bd06/24/2009:svnHewlett-Packard:pnHPCompaq6830s(FR883LA#ABM):pvrF.0F:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP Compaq 6830s (FR883LA#ABM) dmi.product.version: F.0F dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu May 5 21:31:49 2022 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputLVDS VGA-0 xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971916 Title: error in the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1971916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969959] Re: Weird colors after startup (Ubuntu 22.04)
Same here, trying the first stable live release of 22.04. I get a weirdly saturated green-lime combo. Picture attached. VGA: Intel HD Graphics 530 Monitor: HP LE2201w ** Attachment added: "Picture of screen" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969959/+attachment/5582878/+files/20220423_194416.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969959 Title: Weird colors after startup (Ubuntu 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964494] Re: Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs
I agree, a user-configured setting should be honored. Another thing to consider is that according to the Jammy systemd.network man page, the default should be 'ipv6' so one would expect that to be a global default, but it gets overridden for link-local IPs due to this commit. [1] https://manpages.ubuntu.com/manpages/jammy/man5/systemd.network.5.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964494 Title: Setting DuplicateAddressDetection=none doesn't disable DAD for link- local IPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1964494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964494] [NEW] Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs
Public bug reported: A customer reported network disconnections on their storage servers when running 'netplan apply'. The culprit was that they have link-local addresses configured and the Duplicate Address Detection (DAD) mechanism was delaying the interfaces from coming back up. As a workaround we tried to disable DAD for the interfaces but that's not working in Ubuntu 22.04: I've noticed that setting DuplicateAddressDetection=none for an interface with a link-local address (e.g., 169.254.*) via a .network file added to /etc/systemd/network/ doesn't really disable Duplicate Address Detection. OS and package versions: - Description: Ubuntu Jammy Jellyfish (development branch). Release: 22.04 - systemd 249.5-2ubuntu4 Reproducer: --- 1- Set up Ubuntu 22.04 VM 2- Increase systemlog level: mkdir -p /etc/systemd/system/systemd-networkd.service.d/ cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf
[Bug 1960647] [NEW] sound problem on Dell Vostro 3405
Public bug reported: From install xubuntu not sound on my laptop, i following https://help.ubuntu.com/community/SoundTroubleshootingProcedure I found with BIOS nro 146 not show features (microfone for example) and my system show Dummy outputs devices. After upgrade BIOS 149 this features appears!! But not sounds... attach file with info!!! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162 Uname: Linux 5.4.0-99-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: melange1188 F pulseaudio /dev/snd/controlC0: melange1188 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Feb 11 12:42:33 2022 InstallationDate: Installed on 2021-11-19 (83 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: melange1188 F pulseaudio /dev/snd/controlC0: melange1188 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Vostro 3405, Cirrus Logic Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.9 dmi.board.asset.tag: not specified dmi.board.name: 0Y6PDY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.9 dmi.modalias: dmi:bvnDellInc.:bvr1.4.9:bd10/12/2021:svnDellInc.:pnVostro3405:pvr1.4.9:rvnDellInc.:rn0Y6PDY:rvrA00:cvnDellInc.:ct10:cvr1.4.9: dmi.product.family: Vostro dmi.product.name: Vostro 3405 dmi.product.sku: 0A11 dmi.product.version: 1.4.9 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-02-11T11:47:02.161792 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960647 Title: sound problem on Dell Vostro 3405 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1960647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771880] Re: Seahorse unable to import pkcs12 certificates
same problem. LTS Ubuntu 20.04 update today 01-2022, seahorse 3.36-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1771880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958927] [NEW] ubuntu upgrader core
Public bug reported: Removed deadsnakes with ppa-purge, but still the upgrader crashed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 16:10:33 2022 InstallationDate: Installed on 2020-10-22 (459 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2022-01-24 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-01-16T20:07:52.815322 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958927 Title: ubuntu upgrader core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1958927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958687] [NEW] ubuntu upgrader core
Public bug reported: upgrader cores ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:22:48 2022 InstallationDate: Installed on 2020-10-22 (456 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2022-01-21 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-01-16T20:07:52.815322 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958687 Title: ubuntu upgrader core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1958687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956974] [NEW] sound problem on Dell Vostro 3405
Public bug reported: From install xubuntu not sound on my laptop, i following https://help.ubuntu.com/community/SoundTroubleshootingProcedure I found with BIOS nro 146 not show features (microfone for example) and my system show Dummy outputs devices. After upgrade BIOS 149 this features appears!! But not sounds... attach file with info!!! ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "diagnostics file" https://bugs.launchpad.net/bugs/1956974/+attachment/5553111/+files/Diag_out.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956974 Title: sound problem on Dell Vostro 3405 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1956974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
still present in ubuntu 20.04 Linux 5.11.0-40-generic #44~20.04.2-Ubuntu SMP Tue Oct 26 18:07:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) Nov 15 18:37:52 localhost kernel: [ 4754.000821] nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2 Nov 15 18:37:52 localhost kernel: [ 4754.000857] nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084d failed with error -2 Nov 15 18:37:52 localhost kernel: [ 4754.000860] nouveau :01:00.0: msvld: unable to load firmware data Nov 15 18:37:52 localhost kernel: [ 4754.000865] nouveau :01:00.0: msvld: init failed, -19 Nov 15 18:38:01 localhost kernel: [ 4763.095679] nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2 lsmod | grep nouveau nouveau 1986560 38 mxm_wmi16384 1 nouveau drm_ttm_helper 16384 1 nouveau ttm73728 2 drm_ttm_helper,nouveau drm_kms_helper237568 1 nouveau i2c_algo_bit 16384 1 nouveau video 53248 1 nouveau wmi32768 2 mxm_wmi,nouveau drm 548864 18 drm_kms_helper,drm_ttm_helper,ttm,nouveau NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal -- nov 15 18:37:52 X kernel: nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2 nov 15 18:37:52 X kernel: nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084d failed with error -2 nov 15 18:37:52 X kernel: nouveau :01:00.0: msvld: unable to load firmware data nov 15 18:37:52 X kernel: nouveau :01:00.0: msvld: init failed, -19 nov 15 18:38:01 X gnome-shell[12474]: libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so nov 15 18:38:01 X kernel: nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2 nov 15 18:38:01 X kernel: nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084d failed with error -2 nov 15 18:38:01 X kernel: nouveau :01:00.0: msvld: unable to load firmware data nov 15 18:38:01 X kernel: nouveau :01:00.0: msvld: init failed, -19 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751497 Title: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
still present in ubuntu 20.04 Linux 5.11.0-40-generic #44~20.04.2-Ubuntu SMP Tue Oct 26 18:07:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) Nov 15 18:37:52 localhost kernel: [ 4754.000821] nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2 Nov 15 18:37:52 localhost kernel: [ 4754.000857] nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084d failed with error -2 Nov 15 18:37:52 localhost kernel: [ 4754.000860] nouveau :01:00.0: msvld: unable to load firmware data Nov 15 18:37:52 localhost kernel: [ 4754.000865] nouveau :01:00.0: msvld: init failed, -19 Nov 15 18:38:01 localhost kernel: [ 4763.095679] nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2 lsmod | grep nouveau nouveau 1986560 38 mxm_wmi16384 1 nouveau drm_ttm_helper 16384 1 nouveau ttm73728 2 drm_ttm_helper,nouveau drm_kms_helper237568 1 nouveau i2c_algo_bit 16384 1 nouveau video 53248 1 nouveau wmi32768 2 mxm_wmi,nouveau drm 548864 18 drm_kms_helper,drm_ttm_helper,ttm,nouveau NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Nov 15 18:38:01 localhost kernel: [ 4763.095707] nouveau :01:00.0: Direct firmware load for nouveau/nva8_fuc084d failed with error -2 Nov 15 18:38:01 localhost kernel: [ 4763.095710] nouveau :01:00.0: msvld: unable to load firmware data Nov 15 18:38:01 localhost kernel: [ 4763.095715] nouveau :01:00.0: msvld: init failed, -19 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751497 Title: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
** Changed in: linux (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751497 Title: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927519] Re: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory
We have at least a customer on Ubuntu Xenial who hits this somewhat regularly and would very much appreciate this fix getting into SRU as quickly as possible. Would you please consider moving this forward using the fastest path available? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927519 Title: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1927519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890572] Re: USB backend never ends if the printer is not connected
Hi Till, the issue was reported in the Apple repository: https://github.com/apple/cups/issues/5817 I will check whether this was already fixed in OpenPrinting or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890572 Title: USB backend never ends if the printer is not connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached]
I changed that line so that it says: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash drm.debug=0x1e log_buf_len=4M" and follower the rest of the steps. when typing: sudo dmesg | grep "Refresh Rate" on the terminal, nothing really happens. I am not sure I am doing that last step well, since I checked the previous ones. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached]
Hello there, I am having a problem that sounds quite similar to yours. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285 Could you tell me what exactly I must type on terminal to check how my laptop's refresh rate changes (if any), just to check if it behaves like yours. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940285] Re: [Teclast F7] Laptop screen flickering on kernels above 5.4 (not included)
I should have mentioned that the screen blank flashes or flickering, is not the only symptom since there it comes with very little but noticeable "adjustments" of the screen brightness, and then, from time to time, the blinks. This all occurs specially when the PC is being used or working, seems less frequent at idle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940285 Title: [Teclast F7] Laptop screen flickering on kernels above 5.4 (not included) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940285] Re: [Teclast F7] Laptop screen flickering on kernels above 5.4 (not included)
Hello ! I just tried what you suggested on a freshly new and updated installation of Ubuntu 21.10, but the problem persists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940285 Title: [Teclast F7] Laptop screen flickering on kernels above 5.4 (not included) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940780] Re: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04
Hello Daniel, I can open a new bug (in fact I open one not so much ago but for time matters couldn't continue with it). However, as I said, I am running Linux Mint as of now, with Kernel 5.4, and really I've got no intention of switching again right now. Can I report a bug for 5.11 kernel even though I am not running it? I wonder since last time other people helping asked me to upload run an aport-collect command to upload a file (I think), which wouldn't make much sense running a kernel version in which I don't have the screen flickering problem, would it? Anyway, this is the report I am talking about: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285 This is another report opened 3 days ago by another person which seems to be very similar to mine: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1943370 As I said earlier, tell me if I should report the bug, anyway, running Linux Mint now. My intentions are to stick with it for now unless 21.10 Ubuntu calls my attention (which is unlikely since I am sure the screen flickering will persist). Thanks beforehand. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940780 Title: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1940780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940780] Re: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04
I am facing this exact same problem. My laptop runs on an Intel n3450, Intel HD graphics 500 (drivers i915 at least as of now on Linux Mint 20.2, kernel 5.4) I am using as I said Linux Mint 20.2 because every single Linux distribution that runs kernel branches 5.11 or above makes my laptop's screen flicker to the point that it is so frustrating to use, and might be dangerous too. Kernel version 5.10 gives very little flickering and I would say it is usable. I don't remember right now if 5.8 gave me any problem (I believe not), but what I can assure is that 5.11 or above (for instance, 5.13 too) makes the screen flickering appear again, no matter the distribution. On 5.4 it runs perfectly fine. I have no experience on programming. Did you find any solution? Are the kernel developers aware of this problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940780 Title: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1940780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943370] Re: i915 screen flicker
I am facing this exact same problem. My laptop runs on an Intel n3450, Intel HD graphics 500 (drivers i915 at least as of now on Linux Mint 20.2, kernel 5.4) I am using as I said Linux Mint 20.2 because every single Linux distribution that runs kernel branches 5.11 or above makes my laptop's screen flicker to the point that it is so frustrating to use, and might be dangerous too. Kernel version 5.10 gives very little flickering and I would say it is usable. I don't remember right now if 5.8 gave me any problem (I believe not), but what I can assure is that 5.11 or above (for instance, 5.13 too) makes the screen flickering appear again, no matter the distribution. On 5.4 it runs perfectly fine. I have no experience on programming. Did you find any solution? Are the kernel developers aware of this problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943370 Title: i915 screen flicker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1943370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1940285] Re: Laptop screen flickering on kernels above 5.4 (not included)
Excuse me, but which exact .deb file should I download? Thanks beforehand. El mié, 25 ago 2021 a las 4:05, Kai-Heng Feng (<1940...@bugs.launchpad.net>) escribió: > Please test latest mainline kernel: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14-rc7/amd64/ > Headers are not needed. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1940285 > > Title: > Laptop screen flickering on kernels above 5.4 (not included) > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Recently, I installed Ubuntu 21.04 on my laptop and I was having the > same problem I had like with others distros such as Fedora; for some > reason, the screen just ramdonly and briefly turns off, (more like a > flickering) and it also "autoregulates" a the brightness, just a > little bit down and then a little bit up. > > I noticed I don't have this problem on Linux Mint, and I also noticed > that going back to Kernel 5.8 on either Ubuntu 21.04 or 20.04.2 this > problem stops. I have been using Mainline ( > https://github.com/bkw777/mainline ) to install previous kernels (5.8 > and 5.4 wok just fine, but anything above this problem comes again). > > Thanks so much beforehand. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940285 Title: Laptop screen flickering on kernels above 5.4 (not included) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940285] Re: Laptop screen flickering on kernels above 5.4 (not included)
I should especifice also that my laptop (Teclast F7) uses an Intel Celeron n3450 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940285 Title: Laptop screen flickering on kernels above 5.4 (not included) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940285] Re: Laptop screen flickering on kernels above 5.4 (not included)
I had to select a package. Since I have read that problems regarding the kernel should be listed as "linux" (and I think this is the case), that is why I selected that package. ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940285 Title: Laptop screen flickering on kernels above 5.4 (not included) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940285] [NEW] Laptop screen flickering on kernels above 5.4 (not included)
Public bug reported: Recently, I installed Ubuntu 21.04 on my laptop and I was having the same problem I had like with others distros such as Fedora; for some reason, the screen just ramdonly and briefly turns off, (more like a flickering) and it also "autoregulates" a the brightness, just a little bit down and then a little bit up. I noticed I don't have this problem on Linux Mint, and I also noticed that going back to Kernel 5.8 on either Ubuntu 21.04 or 20.04.2 this problem stops. I have been using Mainline ( https://github.com/bkw777/mainline ) to install previous kernels (5.8 and 5.4 wok just fine, but anything above this problem comes again). Thanks so much beforehand. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: flickering laptop screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940285 Title: Laptop screen flickering on kernels above 5.4 (not included) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1940285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692671] Re: intel driver fails to reenable display
it's been more than 4 years. nothing is the same as when this problem happened -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692671 Title: intel driver fails to reenable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1692671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924773] Re: Error calculating upgrade 18.04 to 20.04
** Attachment added: "AARCOS_.jpg" https://bugs.launchpad.net/bugs/1924773/+attachment/5500897/+files/AARCOS_.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924773 Title: Error calculating upgrade 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1924773] Re: Error calculating upgrade 18.04 to 20.04
Hi Ubuntu Team!! I hope you are well, After last dist-upgrade both terminal with a problem not show this event!!!. Many Thanks for advance Best regards On 14/5/21 18:28, Brian Murray wrote: > Thanks for taking the time to report this upgrade failure. There is > currently a new version of the release upgrader available in -proposed > which may resolve the error you've encountered. Please run the following > command to test the new version of the upgrader: > >do-release-upgrade -p > > Please lets us know the results in this bug report. Thanks again and > good luck! > > ** Changed in: ubuntu-release-upgrader (Ubuntu) > Status: New => Incomplete > > ** Tags added: lp-1928397 > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924773 Title: Error calculating upgrade 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924773] [NEW] Error calculating upgrade 18.04 to 20.04
Public bug reported: Error upgrade 18.04 to 20.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu Date: Fri Apr 16 11:42:51 2021 InstallationDate: Installed on 2019-09-05 (588 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=es_AR TERM=xterm-256color PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-04-16 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924773 Title: Error calculating upgrade 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923677] [NEW] package grub-efi-amd64-signed 1.167+2.04-1ubuntu44 failed to install/upgrade: el subproceso instalado paquete grub-efi-amd64-signed script post-installation devolvió el código de s
Public bug reported: This occurred during system installation from usb on Asus computer ProblemType: Package DistroRelease: Ubuntu 20.10 Package: grub-efi-amd64-signed 1.167+2.04-1ubuntu44 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 13 18:45:16 2021 ErrorMessage: el subproceso instalado paquete grub-efi-amd64-signed script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2021-04-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.167+2.04-1ubuntu44 failed to install/upgrade: el subproceso instalado paquete grub-efi-amd64-signed script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923677 Title: package grub-efi-amd64-signed 1.167+2.04-1ubuntu44 failed to install/upgrade: el subproceso instalado paquete grub-efi-amd64-signed script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1923677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890572] Re: USB backend never ends if the printer is not connected
Hi Sebastian, the patch set the job state to backend error. I don't think openprinting is the right error here. The problem is in the backend (the USB backend) when it's not possible to communicate with a USB printer. This usually means that the printer is not connected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890572 Title: USB backend never ends if the printer is not connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923109] [NEW] Power daemon does not sense when AC adapter is plugged and shuts the machine down
Public bug reported: If any power-related app is open, or if I let the "low battery" notification go away, the control center does not report the connection of an AC Adapter and eventually powers the machine down. uname -a returns: Linux maelstrom-x509dj-m509dj 5.8.0-48-generic #54-Ubuntu SMP Fri Mar 19 14:25:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux sudo dmesg | tail returns: [sudo] password for maelstrom: [3.835417] ---[ end trace d10ad7cd4552be52 ]--- [4.566546] input: HD-Audio Generic Headphone as /devices/pci:00/:00:08.1/:03:00.6/sound/card1/input21 [4.574762] ACPI Warning: \_SB.PCI0.GPP0.VGA._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20200528/nsarguments-59) [7.687695] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready [8.797016] rfkill: input handler disabled [ 16.687324] Bluetooth: RFCOMM TTY layer initialized [ 16.687331] Bluetooth: RFCOMM socket layer initialized [ 16.687340] Bluetooth: RFCOMM ver 1.11 [ 16.870417] rfkill: input handler enabled [ 20.199148] rfkill: input handler disabled ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 8 16:36:51 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-03-02 (37 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923109 Title: Power daemon does not sense when AC adapter is plugged and shuts the machine down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1923109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910149] Re: adb devices crashes with munmap_chunk(): invalid pointer
same issue, also after clearing ~/.android
[ 7521.901775] usb 1-2: new high-speed USB device number 9 using xhci_hcd
[ 7522.033001] usb 1-2: New USB device found, idVendor=18d1, idProduct=4ee7,
bcdDevice= 4.14
[ 7522.033004] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7522.033005] usb 1-2: Product: Mi 9T Pro
[ 7522.033007] usb 1-2: Manufacturer: Xiaomi
[ 7522.033008] usb 1-2: SerialNumber: ea48f411
$ grep 18d1 /lib/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ENV{adb_user}="yes"
$ dpkg -S /lib/udev/rules.d/51-android.rules
android-sdk-platform-tools-common: /lib/udev/rules.d/51-android.rules
$ dpkg -l android-sdk-platform-tools-common | tail -n1
ii android-sdk-platform-tools-common 27.0.0+12all Tools for
interacting with an Android platform - Common files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910149
Title:
adb devices crashes with munmap_chunk(): invalid pointer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-platform-system-core/+bug/1910149/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872760] Re: i915 - after return from suspend display is flickering / *ERROR* CPU pipe A FIFO underrun
The same issue on my Lenovo T14s, frequently hanging after suspend. I'm using Ubuntu 20.04, with HWE kernel version 5.8.0-40-generic. I have two external monitors with 1980x1080 res, connected through a 2xHDMI to USB-C connector using DisplayLink. This is really annoying! Are there any efforts being made to provide definitive root cause analysis and ship the solution into an upcoming kernel version? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872760 Title: i915 - after return from suspend display is flickering / *ERROR* CPU pipe A FIFO underrun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910799] [NEW] Tarjeta de red problemas
Public bug reported: Por alguna razon no quiere conocer la tarjeta de red, ahora que lo reinstalè, estaba funcionando antes de forma normalque puedo hacer?? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 Date: Fri Jan 8 14:39:30 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed noprompt boot=casper cdrom-detect/try-usb=true quiet splash iso-scan/filename=/multiboot/ubuntu-20.04.1-desktop-amd64/ubuntu-20.04.1-desktop-amd64.iso quiet -- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910799 Title: Tarjeta de red problemas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1910799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846699] Re: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm
Hi @Sebastien, I don't really understand the last comment. What do you mean by "However, I am closing it because the bug has been fixed in the latest development version of Ubuntu."? The issue is present in the last version of the package for Ubuntu 18.04 LTS. The problem is that we can NOT migrate our systems to Ubuntu 20.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846699 Title: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841793] Re: Don't update to 2.65.3
Thanks @sebastien! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841793 Title: Don't update to 2.65.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1841793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841793] Re: Don't update to 2.65.3
Please can somebody indicate whether this is still an issue or not? We have some products that cannot be upgraded to Ubuntu 20.04 yet, and the version of Glibmm in Ubuntu 1804 (Glibmm 2.56) has some important compatibility issues after some design changes in glib. The mechanisms to solve this issue were introduced in Glibmm 2.60: https://developer.gnome.org/glibmm/2.60/classGlib_1_1ExtraClassInit.html I would like to ask to please increase the version in Ubuntu 18.04, to at least Glibmm 2.60 or to include a patch to introduce the solution. The patch is included in this issue report: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841793 Title: Don't update to 2.65.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1841793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846699] Re: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm
HI, can someone please sponsor this patch or the upgrade of the Glibmm package to at least version 2.60? We have some products that are affected by this problem, and we can not upgrade to Ubuntu 20.04 yet. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846699 Title: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899045] [NEW] I manually created a 200Mib EFI System Partition and like a 100 Gib Ext4 one for /, maybe it was the Third Parties things idk
Public bug reported: I manually created a 200Mib EFI System Partition and like a 100 Gib Ext4 one for /, maybe it was the Third Parties things idk ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 8 15:46:22 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201007) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899045 Title: I manually created a 200Mib EFI System Partition and like a 100 Gib Ext4 one for /, maybe it was the Third Parties things idk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1899045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883798] Re: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instanc
Hi. I installed packettracer. Is there any solution? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883798 Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg- turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1883798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895757] Re: Terminal hangs running sudo when "use_pty" is set in /etc/sudoers
** Also affects: sudo (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895757 Title: Terminal hangs running sudo when "use_pty" is set in /etc/sudoers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1895757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895757] Re: Terminal hangs running sudo when "use_pty" is set in /etc/sudoers
** Description changed:
An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running
a command using 'sudo' when 'use_pty' is set in /etc/sudoers.
Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):
1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
2) Ensure that /etc/sudoers has the following line (add this line if not
present)
Defaults use_pty
- 3) Execute the following:
+ 3) Execute the following (test 'sudo' command):
for i in {1..10}; do sudo -- cat /var/log/syslog; done
The terminal hangs and the following backtrace is obtained:
(gdb) bt
#0 0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1,
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2 sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0)
at ../../../lib/util/event_poll.c:155
#3 0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0,
flags=flags@entry=0) at ../../../lib/util/event.c:617
#4 0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false)
at ../../src/exec_pty.c:1537
#5 0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at
../../src/exec_pty.c:697
#6 exec_pty (details=details@entry=0x55d01591e0e0 ,
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
#7 0x55d015701178 in sudo_execute (details=0x55d01591e0e0
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
#8 0x55d01570e15b in run_command (details=0x55d01591e0e0
) at ../../src/sudo.c:968
#9 0x55d0156ff9a0 in main (argc=, argv=,
envp=) at ../../src/sudo.c:294
A similar (most likely the same) bug has been reported here
https://access.redhat.com/solutions/3404401.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895757
Title:
Terminal hangs running sudo when "use_pty" is set in /etc/sudoers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1895757/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895757] Re: Terminal hangs running sudo when "use_pty" is set in /etc/sudoers
** Description changed:
An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running
a command using 'sudo' when 'use_pty' is set in /etc/sudoers.
- Steps to reproduce:
+ Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):
1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
2) Ensure that /etc/sudoers has the following line (add this line if not
present)
Defaults use_pty
3) Execute the following:
for i in {1..10}; do sudo -- cat /var/log/syslog; done
The terminal hangs and the following backtrace is obtained:
(gdb) bt
#0 0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1,
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2 sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0)
at ../../../lib/util/event_poll.c:155
#3 0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0,
flags=flags@entry=0) at ../../../lib/util/event.c:617
#4 0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false)
at ../../src/exec_pty.c:1537
#5 0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at
../../src/exec_pty.c:697
#6 exec_pty (details=details@entry=0x55d01591e0e0 ,
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
#7 0x55d015701178 in sudo_execute (details=0x55d01591e0e0
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
#8 0x55d01570e15b in run_command (details=0x55d01591e0e0
) at ../../src/sudo.c:968
#9 0x55d0156ff9a0 in main (argc=, argv=,
envp=) at ../../src/sudo.c:294
A similar (most likely the same) bug has been reported here
https://access.redhat.com/solutions/3404401.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895757
Title:
Terminal hangs running sudo when "use_pty" is set in /etc/sudoers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1895757/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895757] [NEW] Terminal hangs running sudo when "use_pty" is set in /etc/sudoers
Public bug reported:
An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running
a command using 'sudo' when 'use_pty' is set in /etc/sudoers.
Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):
1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
2) Ensure that /etc/sudoers has the following line (add this line if not
present)
Defaultsuse_pty
3) Execute the following:
for i in {1..10}; do sudo -- cat /var/log/syslog; done
The terminal hangs and the following backtrace is obtained:
(gdb) bt
#0 0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2 sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0) at
../../../lib/util/event_poll.c:155
#3 0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0,
flags=flags@entry=0) at ../../../lib/util/event.c:617
#4 0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false)
at ../../src/exec_pty.c:1537
#5 0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at
../../src/exec_pty.c:697
#6 exec_pty (details=details@entry=0x55d01591e0e0 ,
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
#7 0x55d015701178 in sudo_execute (details=0x55d01591e0e0
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
#8 0x55d01570e15b in run_command (details=0x55d01591e0e0
) at ../../src/sudo.c:968
#9 0x55d0156ff9a0 in main (argc=, argv=,
envp=) at ../../src/sudo.c:294
A similar (most likely the same) bug has been reported here
https://access.redhat.com/solutions/3404401.
** Affects: sudo (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895757
Title:
Terminal hangs running sudo when "use_pty" is set in /etc/sudoers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1895757/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890572] Re: USB backend never ends if the printer is not connected
We have prepared a patch for the package in Ubuntu 18.04 (CUPS 2.2.7). We would like to request to include a solution like this for at least Ubuntu 18.04. We also made a pull request in the official CUPS repository: https://github.com/apple/cups/issues/5817 https://github.com/apple/cups/pull/5818 However, we don't have plans to upgrade or change the distribution we use (Ubuntu 18.04), and this issue is affecting us considerably. ** Bug watch added: github.com/apple/cups/issues #5817 https://github.com/apple/cups/issues/5817 ** Patch added: "usb-libusb.c.patch" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+attachment/5399506/+files/usb-libusb.c.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890572 Title: USB backend never ends if the printer is not connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890763] [NEW] I suspect Firefox cause journal problem, doing lags of keyboard and mouse input, or slow apps
Public bug reported: I have a new installation of Ubuntu 20.04 LTS. Two weeks ago I experienced several issues: -slow boot -disk failures (inodes corrupted, superblock invalid, read-only at start) -Firefox slower to respond at start, can't get the previous session -systemd-journald error trying to write on read-only filesystem -/tmpfs read-only -/var/log/journal with 1.6 GB -snap-store process with the highest memory use Yesterday I have to abandon the use of this Ubuntu 20.04, because the lack of trust Today, I trim the max size of journal files (100 MB), change resolution of display and avoid using Firefox (instead using Chromium); however, this report invoke Firefox; during 2 hours I been working as smooth and fine as always. Finally, I use Ubuntu in a diary basis; in this device I have versions 16.04, 18.04 and 20.04. Only 20.04 give this problems. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alejandro 2458 F pulseaudio /dev/snd/controlC0: alejandro 2458 F pulseaudio BuildID: 20200720193547 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 21:48:33 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:725 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-05-19 (79 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.64 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:725 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=79.0/20200720193547 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A4CN40WW (V 2.09) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5B3 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688SDK0J40688 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-75 dmi.modalias: dmi:bvnLENOVO:bvrA4CN40WW(V2.09):bd08/24/2015:svnLENOVO:pn80EC:pvrLenovoZ50-75:rvnLENOVO:rnLancer5B3:rvrSDK0J40688SDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoZ50-75: dmi.product.family: IDEAPAD dmi.product.name: 80EC dmi.product.sku: LENOVO_MT_80EC0_BU_idea_FM_Lenovo Z50-75 dmi.product.version: Lenovo Z50-75 dmi.sys.vendor: LENOVO ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890763 Title: I suspect Firefox cause journal problem, doing lags of keyboard and mouse input, or slow apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1890763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890572] Re: USB backend never ends if the printer is not connected
** Description changed:
- USB backend never ends if the printer is not connected. we have been
+ USB backend never ends if the printer is not connected. We have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
- fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
- while ((g.printer = find_device(print_cb, uri)) == NULL)
- {
- _cupsLangPrintFilter(stderr, "INFO",
-_("Waiting for printer to become available."));
- sleep(5);
- }
+ fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
+ while ((g.printer = find_device(print_cb, uri)) == NULL)
+ {
+ _cupsLangPrintFilter(stderr, "INFO",
+ _("Waiting for printer to become available."));
+ sleep(5);
+ }
```
It's also easy to test by invoking the backend by hand:
-
```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...
```
- Setting a job timeout policy or stopping the job by hand are not options
- for us. We can have job that take up to an hour to complete.
+ Setting a work timeout policy or manually stopping work are not options
+ for us. We may have jobs that take up to an hour to complete.
** Description changed:
USB backend never ends if the printer is not connected. We have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
_cupsLangPrintFilter(stderr, "INFO",
_("Waiting for printer to become available."));
sleep(5);
}
```
It's also easy to test by invoking the backend by hand:
```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
- DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
+ DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...
```
Setting a work timeout policy or manually stopping work are not options
for us. We may have jobs that take up to an hour to complete.
** Description changed:
USB backend never ends if the printer is not connected. We have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
_cupsLangPrintFilter(stderr, "INFO",
_("Waiting for printer to become available."));
sleep(5);
}
```
It's also easy to test by invoking the backend by hand:
```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
-
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...
```
- Setting a work timeout policy or manually stopping work are not options
+ Setting a job timeout policy or manually stopping work are not options
for us. We may have jobs that take up to an hour to complete.
** Description changed:
USB backend never ends if the printer is not connected. We have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while
[Bug 1890572] [NEW] USB backend never ends if the printer is not connected
Public bug reported:
USB backend never ends if the printer is not connected. we have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
_cupsLangPrintFilter(stderr, "INFO",
_("Waiting for printer to become available."));
sleep(5);
}
```
It's also easy to test by invoking the backend by hand:
```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...
```
Setting a job timeout policy or stopping the job by hand are not options
for us. We can have job that take up to an hour to complete.
** Affects: cups (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890572
Title:
USB backend never ends if the printer is not connected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888436] [NEW] package freecad-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/freecad-doc/ThirdPartyLibraries.html', which is also in package freecad-doc 1:
Public bug reported: Sometimes happen ProblemType: Package DistroRelease: Ubuntu 20.04 Package: freecad-common (not installed) ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 13 17:05:56 2020 ErrorMessage: trying to overwrite '/usr/share/doc/freecad-doc/ThirdPartyLibraries.html', which is also in package freecad-doc 1:0.17.13541-1ppa10~ubuntu18.04.1 InstallationDate: Installed on 2017-05-05 (1173 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: freecad Title: package freecad-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/freecad-doc/ThirdPartyLibraries.html', which is also in package freecad-doc 1:0.17.13541-1ppa10~ubuntu18.04.1 UpgradeStatus: Upgraded to focal on 2020-05-21 (61 days ago) ** Affects: freecad (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888436 Title: package freecad-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/freecad- doc/ThirdPartyLibraries.html', which is also in package freecad-doc 1:0.17.13541-1ppa10~ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1888436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846699] Re: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm
Patch for version 2.56 that incorporates a fix related to the theme management in version 2.60 ** Patch added: "Patch for version 2.56 that incorporates a fix related to the theme management in version 2.60" https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+attachment/5390142/+files/0001-Object-construction-Add-custom-class-init-and-instan.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846699 Title: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846699] Re: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm
Can anybody look at this issue? We have a patch to solve this in the Ubuntu 18.04 package (version v2.56) and we are also able to compile and use version 2.60. However, we will like to be included in the official distribution files. This simplifies our deployment. If we provide the patch of the upgrade to v2.6x will anybody review it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846699 Title: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13
I've got this problem with a shiny new TB3 docking/eGPU (razer core x chroma) on 20.04. it has 3 ASM1142 controllers. ** Attachment added: "sudo lshw -short" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750/+attachment/5389980/+files/lshw_short.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667750 Title: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1667750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
problem still happening in latest 20.04 with and without backport- iwlwifi-dkms -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858077] Re: Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [8086:2526] subsystemid [8086:0014] crash, lock and restart, Error sending STATISTICS_CMD: time out after 2000ms
problem still present in latest 20.04 including backport-iwlwifi-driver. ubuntu mainline kernels aren't an option for me as they aren't signed and can't boot with them -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858077 Title: Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [8086:2526] subsystemid [8086:0014] crash, lock and restart, Error sending STATISTICS_CMD: time out after 2000ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]
and btw, installing backport-iwlwifi-dkms doesn't fix it either. it's hard to digest one need to manually upgrade the kernel when using the latest LTS or a known (and fixed upstream) bug on a very popular wifi driver will take your whole USB bus out of service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848921 Title: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]
the problem is still present on the latest 20.04 (Linux 5.4.0-40-generic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848921 Title: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846998] Re: close button doesn't fill the corner on maximized window
Experiencing this again on Ubuntu MATE 20.04 LTS, with MATE 1.24.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846998 Title: close button doesn't fill the corner on maximized window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1846998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
I hope that soon it will be fix on the next update kernel :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
@Romain No, like you said I can not control the volume with this solution, sounds great but still have this problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
I just follow the mentioned before: sudo apt install install alsa-tools then run sudo hda-verb /dev/snd/hwC0D0 0x17 SET_CONNECT_SEL 1 For the changes take effects after reboot: sudo gedit /etc/rc.local and put this on it: #!/bin/sh -e hda-verb /dev/snd/hwC0D0 0x17 SET_CONNECT_SEL 1 exit 0 Now give permission to the file: sudo chmod +x /etc/rc.local reboot and that's it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
@Michele finally it works with your recommendation, I created a script with this commmand to iniciate on starup, thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883408] [NEW] package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o
Public bug reported: no deja de molesrae ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cups-client 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 13 06:32:25 2020 ErrorMessage: no se pudieron copiar los datos extraídos de './usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2020-06-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Latitude E6400 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: cups Title: package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A34 dmi.board.name: 0G866N dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0G866N:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883408 Title: package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1883408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883409] [NEW] package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o
Public bug reported: no deja de molesrae ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cups-client 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 13 06:32:25 2020 ErrorMessage: no se pudieron copiar los datos extraídos de './usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2020-06-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Latitude E6400 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: cups Title: package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A34 dmi.board.name: 0G866N dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0G866N:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883409 Title: package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1883409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
did somebody resolve the problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
@mikelito @darko Lukic improve the sound but still not at 100%, with fedora and windows sounds is better -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
thnak you ash, I switched to fedora 32 and no problem, I will wait until Ubuntu resolve the problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
Hi, I have the same problem here with my lenovo thinkpad x1 carbon 7th, a brand new laptop switched to ubuntu but the sound is very poor, I will wait for the solution, thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878934] [NEW] wrong atime and mtime in file config.h.in created using autoheader in a bind-mounted directory
Public bug reported: 1) ❯ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 2) ❯ apt-cache policy autoconf autoconf: Installed: 2.69-11 Candidate: 2.69-11 Version table: *** 2.69-11 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://ar.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status 3) expected behavior: atime and mtime of file config.h.in file created using autoheader in a bind-mounted directory are representative of the time at which the file was created 4) actual behavior: atime and mtime of file config.h.in file created using autoheader in a bind-mounted directory are rounded to the second --- Steps to reproduce the bug (check for relevant information in other issue comments): https://github.com/docker/for- linux/issues/990#issuecomment-620538818 ** Affects: autoconf (Ubuntu) Importance: Undecided Status: New ** Tags: autoconf autoheader bind filesystem kernel mount -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878934 Title: wrong atime and mtime in file config.h.in created using autoheader in a bind-mounted directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autoconf/+bug/1878934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876594] Re: totem doesn't start on Wayland: Error 71 (Error de protocolo) dispatching to Wayland display
WAYLAND_DEBUG=1 totem >& totem-wayland-log.txt asked in #3 ** Attachment added: "WAYLAND_DEBUG=1 totem >& totem-wayland-log.txt" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1876594/+attachment/5366162/+files/totem-wayland-log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876594 Title: totem doesn't start on Wayland: Error 71 (Error de protocolo) dispatching to Wayland display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1876594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876594] [NEW] totem doesn't start on Wayland
Public bug reported: Gdk-Message: 12:33:12.232: Error 71 (Error de protocolo) dispatching to Wayland display. This error is only visible when starting Totem from Terminal. Otherwise, Totem quietly doesn't start. vlc is working fine. I'm using Ubuntu 20.04 with Gnome (not Gnome on Xorg). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun May 3 12:23:48 2020 InstallationDate: Installed on 2013-07-11 (2487 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: Upgraded to focal on 2020-04-23 (9 days ago) ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Summary changed: - totem don't start on Wayland + totem doesn't start on Wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876594 Title: totem doesn't start on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1876594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875539] [NEW] debuguer crash
Public bug reported: when i try to run the debug to check te upgrade version trouble it crash ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu Date: Mon Apr 27 23:29:12 2020 InstallationDate: Installed on 2017-11-12 (897 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-04-28 (0 days ago) modified.conffile..etc.update-manager.release-upgrades: [modified] mtime.conffile..etc.update-manager.release-upgrades: 2020-04-27T23:18:24.586124 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875539 Title: debuguer crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1875539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
Related bug: * bug 1829625: Vagrant box startup timeout due to no serial port -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814481] Re: Keychron K1 keyboard not working
good idea, thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: Keychron K1 keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814481] Re: bluetooth keyboard not working
@vanvugt, shouldn't that be after actually merging the fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: bluetooth keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814481] Re: bluetooth keyboard not working
I can confirm https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/comments/19 fixed it. thanks a lot @eferox! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: bluetooth keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806263] Re: MariaDB 10.1 server won't start when MySQL 5.7 server has been previously installed
Just to thank you all. I just hit this problem, solved it and in the process learned something about apparmor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806263 Title: MariaDB 10.1 server won't start when MySQL 5.7 server has been previously installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1806263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849542] Re: Thunderbird empty after update to 19.10
I got it. See it attached. ** Attachment added: "faulty file" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+attachment/5299645/+files/global-messages-db.sqlite -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849542 Title: Thunderbird empty after update to 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849542] Re: Thunderbird empty after update to 19.10
Just deleted global-messages-db.sqlite and now it looks like it works fine. I hopê I didn't loose anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849542 Title: Thunderbird empty after update to 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849542] [NEW] Thunderbird empty after update to 19.10
Public bug reported: HELP Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched Thunderbird and the interface is empty. No emails, no folders, no calendar, I can't even open the "account settings" window. This is a complete disaster. I need thunderbird for my work. If I launch TB form terminal I get this: lalejand@Gedeon:~$ thunderbird JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined TypeError: aAttrDef.objectNounDef is undefined -- Exception object -- * -- Stack Trace -- defineAttribute@resource:///modules/gloda/gloda.js:1922:5 defineAttributes@resource:///modules/gloda/fundattr.js:71:35 init@resource:///modules/gloda/fundattr.js:43:12 @resource:///modules/gloda/everybody.js:13:15 @resource:///modules/gloda/public.js:8:57 nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32 createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19 glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16 JavaScript error: chrome://messenger/content/messenger.xul, line 1: TypeError: QuickFilterBarMuxer is undefined JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: TypeError: TagUtils is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined What can I do ? Release: Ubuntu 19.10 Package version: 1:68.1.2+build1-0ubuntu ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849542 Title: Thunderbird empty after update to 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
Hi, Same problem here. I want to skip the GRUP so I modify the grub file, but once I run the command sudo update-grub the terminal show me the same issue. Thanks and if I can do anything tell me. Alex -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1834250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841793] Re: Don't update to 2.631
Thank you for your answer Jeremy. Now it's clear to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841793 Title: Don't update to 2.631 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1841793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846998] [NEW] close button doesn't fill the corner on maximized window
Public bug reported: I'm experiencing exactly the same as described here: https://github.com /mate-desktop/mate-themes/issues/117 in ubuntu-mate 18.04 with 'Ambiant-MATE' theme. Mate version 1.20.1 On maximized windows, the close button doesn't fill the corner, and it's a bit annoying. ** Affects: ubuntu-mate-artwork (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846998 Title: close button doesn't fill the corner on maximized window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1846998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846699] [NEW] Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm
Public bug reported: In GTK+ 3.20 the theming mechanics was heavily changed. https://developer.gnome.org/gtk3/stable/ch32s10.html One of the major changes was the use of element names much more than style classes. For this the function gtk_widget_class_set_css_name() was added to t he API and used to assign the element names. However, this was not added in GTKmm, making impossible to assign element names in custom widget, and no automatically assignment was developed in GTKmm's Widget class in order to be able to identify widget classes in the theming system (CSS). The problem was discussed and tracked up to Glibmm in GNOME bug tracking system: https://gitlab.gnome.org/GNOME/gtkmm/issues/17 https://gitlab.gnome.org/GNOME/glibmm/issues/33 The issues are due to the lack of the mechanism to call gtk_widget_class_set_css_name() function in the instance init function. This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this version and it's affecting some of our products. We have applied a patch to the current version (2.56) of Glibmm2.4 in Ubuntu 18.04 successfully, but I would like to ask you to consider upgrading the version of Glibmm in the official repository or apply the patch. ** Affects: glibmm2.4 (Ubuntu) Importance: Undecided Status: New ** Description changed: In GTK+ 3.20 the theming mechanics was heavily changed. https://developer.gnome.org/gtk3/stable/ch32s10.html One of the major changes was the use of element names much more than style classes. For this the function gtk_widget_class_set_css_name() was added to t he API and used to assign the element names. However, this was not added in GTKmm, making impossible to assign element names in custom widget, and no automatically assignment was developed in GTKmm's Widget class in order to be able to identify widget classes in the theming system (CSS). The problem was discussed and tracked up to Glibmm in GNOME bug tracking system: https://gitlab.gnome.org/GNOME/gtkmm/issues/17 https://gitlab.gnome.org/GNOME/glibmm/issues/33 The issues are due to the lack of the mechanism to call gtk_widget_class_set_css_name() function in the instance init function. This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this version and it's affecting some of our products. We have applied a patch to the current version (2.56) of Glibmm2.4 in - Ubuntu 18.04 successfully, but I would like to ask considered upgrading - the version of Glibmm in the official repository or apply the patch. + Ubuntu 18.04 successfully, but I would like to ask you to consider + upgrading the version of Glibmm in the official repository or apply the + patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846699 Title: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841793] Re: Don't update to 2.61.1
Good morning Sebastien, can you please describe why is it a problem to upgrade Glibmm? We are affected by an issue in the current version (2.58). After some changes in GTK+ theme mechanisms in order to be able to configure the CSS class names properly it is important to be able to call gtk_widget_class_set_css_name() in the object instance init function. However, this was not possible until Glibmm team add the support to this in version 2.60. Without these change there is no way to solve the problem. The discussion about this can be found in GNOME issue tracking: https://gitlab.gnome.org/GNOME/glibmm/issues/33 https://gitlab.gnome.org/GNOME/gtkmm/issues/17 ** Bug watch added: gitlab.gnome.org/GNOME/glibmm/issues #33 https://gitlab.gnome.org/GNOME/glibmm/issues/33 ** Bug watch added: gitlab.gnome.org/GNOME/gtkmm/issues #17 https://gitlab.gnome.org/GNOME/gtkmm/issues/17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841793 Title: Don't update to 2.61.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1841793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
I confirm that the problem persists with kernel 5.2.9 on HP Spectre x360. I am using kernel 5.1.9, which has no problem. In addition, kernel 5.1.9 with linux-firmware-20190815.07b925b-1 has a problem with iwlwifi, so I had also to downgrade it to linux- firmware-20190618.acb56f2-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories
Good morning Murray, we performed some test and everything looks fine. Thank you very much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830629 Title: Errors when extracting ZIP files. It can not differentiate between files and directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories
Thank you Brian, We are going to be testing it during this week. I will let you know the results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830629 Title: Errors when extracting ZIP files. It can not differentiate between files and directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
I got the same bug on the 5.2 kernel in my HP Spectre x360. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
Hi, I have a HP Spectre x360 13t-ap000, with the exact same problem. I also have NVMe and it drains lots of power under s2idle, and the only option I have in /sys/power/mem_sleep is that one. I am running Arch Linux. $ uname -a Linux behemoth 5.1.8-arch1-1-ARCH #1 SMP PREEMPT Sun Jun 9 20:28:28 UTC 2019 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories
One important note here, The defect is only present in version 3.2.2 (Bionic official version now). Previous and next version do work properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830629 Title: Errors when extracting ZIP files. It can not differentiate between files and directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories
HI Sebastien, Sure. Here is a zip file that it's very easy to use to reproduce the defect. The defect s not in the bsdtar, it's in libarchive. However, since bsdtar depends on libarchive, this can be used to demonstrate the problem as someone reports in the GitHub issue report: https://github.com/libarchive/libarchive/issues/822 If you try to extract the content with bsdtar: # bsdtar -vxf example.zip You will see and error, and if you look to the result in the filesystem, that 'ABCD_1234' and 'empty' are created as files instead of directories. If you try the same operation using unzip in other directory (or after cleaning the previous operation): # unzip example.zip You will see the right result (ABCD_1234 and empty directories). Thanks for take care of this, Alejandro ** Attachment added: "example.zip" https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+attachment/5268728/+files/example.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830629 Title: Errors when extracting ZIP files. It can not differentiate between files and directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791219] Re: Symbolic link to src.zip in openjdk-11-source points to an invalid location
Workaround 2 (alternative for #2): ``` cd /usr/lib/jvm/openjdk-*/lib sudo bash -c 'mv src.zip ..; ln -s ../src.zip src.zip' ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791219 Title: Symbolic link to src.zip in openjdk-11-source points to an invalid location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1791219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791219] Re: Symbolic link to src.zip in openjdk-11-source points to an invalid location
Hi, Sun/Oracle always deployed src.zip in the root of their jdk directories, so the problem here is with openjdk-*-source package, so IMHO: 1. openjdk-lts package should be left as it's (the src.zip symlink is coherent). 2. lib/src.zip file from openjdk-*-source package should be moved from lib/ to the parent directory. Regards, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791219 Title: Symbolic link to src.zip in openjdk-11-source points to an invalid location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1791219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754702] Re: Delay before you can type after switching input source
I have one more update. I could not use ubuntu 18.04 with this bug, so since then, I have been working on ubuntu 16.04 with unity. Yesterday I tried ubuntu 19.04 on a live usb and after configure to my usual setting, the bug was not present. I proceeded to install in on my computer, and I found the bug again. I tried the same procedure and I got the same results. Therefore, I am guessing it could be some configuration file somewhere. After backing up my files, I did a clean install and now the bug is nowhere to be found. I could not determine what it was, but I am thinking it was something in the transition to gnome was not compatible. I am using 19.04 with no problem now, working perfectly and very surprised at how much the desktop has evolved in over a year. Beautiful and fast! kudos to everyone involved. I originally filed this bug, so I am not sure if it can be marked as not in disco dingo. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754702 Title: Delay before you can type after switching input source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1773859] Re: upgrades to 18.04 fail
I ended up uninstalling everything and installing the 18.04 from sctratch.Thanks for your help On Thursday, April 11, 2019, 12:26:08 PM GMT-3, José Enrique <1773...@bugs.launchpad.net> wrote: Hola creo recordar que utilicé estos comandos: sudo mv / usr / share / dbus-1 / system- servicios / org.freedesktop .systemd1. servicio / usr / share / dbus-1 / system- servicios / org.freedesktop .systemd1. Servicio. bak sudo apt-get install -f sudo apt dist-upgrade sudo apt autoremove A mi me funcionó correctamente, pero no lo almacené. Puede ser otro problema con el mismo resultado. Otra solución, que apliqué en un laptop fue sacar un back-up de los archivos de usuario, documentos, descargas... Y reinstalar la nueva versión desde 0 Sañudos El jue., 11 abr. 2019 0:45, loluchayjose <1773...@bugs.launchpad.net> escribió: > Bueno, ninguna de las soluciones aquí está muy clara. Una de ellas es > "sudo apt purge gdm etc."... "etc." que? > > Varios dicen "borrar"... borrar como? > > Tu dijiste: "I solved problem sttoping services and erasing systemd-shim > upon console. > After I could updating my pc, also, from console"... Qué servicios > paraste, y como? Tengo que hacerlo en Safe Mode? > > Uno de los últimos dice: "The upload of systemd that was purported to > fix this bug report was superseded by a security update of systemd so > the fix is no longer available." Así que por lo que se ve, esa solucion > ya no sirve. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1792241). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > Triaged > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > > * Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > > * Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > > * monitor drop-off of upgrades with below reported problem > > * Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial, ie. > > lxc launch ubuntu-daily:xenial test-shim-upgrade > lxc exec test-shim-upgrade > apt update > apt install systemd-shim > wget > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > apt install ./systemd-shim_10-3_amd64.deb > sed 's/xenial/bionic/' -i /etc/apt/sources.list > apt update > apt install systemd > > this currently passes, however, systemd-shim remains installed. It > should be removed instead. Apt install systemd should have lines like > this: > > The following packages will be REMOVED: > systemd-shim > ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > ... > > > [Regression Potential] > > * systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > > * original bug report > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg: error processing package systemd-shim (--remove): > subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: > systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to
