[Bug 2064559] Re: Screen clicks not working when app page maximised
*** This bug is a duplicate of bug 1181666 *** https://bugs.launchpad.net/bugs/1181666 ** This bug has been marked a duplicate of bug 1181666 gnome-shell randomly blocks mouse clicks from working in app windows -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064559 Title: Screen clicks not working when app page maximised To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
I opened a similar bug and @vanvugt advised me to come here. I read everything and will try the PPA if need be. But I'm using a driver that nobody mentioned, which was selected by Dell who assembled the machine and installed the OS. On Nvidia driver section, I'm using "Set the power ondemand mode by default from oem-fix-gfx-nvidia-ondemandmode". I also have drives 535 and 470 available in the menu, but when I install them, my default setting disappears. I had to fully reinstall the OS to get it back. Nvidia themselves advise on their download page to not necessarily use their proprietary drivers on some Linux distribs, so I stuck with my default driver. Will the PPA and the mutter downgrade be of use with this default setting ? Also, installing proprietary pilot from the Software & update menu raised an error, so I aborted the process. I'm running : - Ubuntu 22.4.04 LTS - GNOME 42.9 (latest official update) - X11 - NVIDIA T400 4GB 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/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061585] [NEW] Everything laggy, file browsing in nautilus and terminal completion
Public bug reported: I reinstalled Ubuntu22.04 as it was in factory settings, and everything ran smoothly and fast. I then installed 1.3Go of updates, including the gnome-42-2204 update and everything started to run slow, and nautilus started freezing. I tried to look online for a fix, and everyone pointed to gnome 0+git.510a601 being the issue. I also updated my core22 to version 20240111. This page is an example of the issue I'm having : https://discourse.ubuntu.com/t/very-lagging-slow-after-latest-kernel- gnome-upgrade-22-04-3/37881/9 I'm on Ubuntu 20.04.4 LTS with a brand new machine : 64Go RAM, Intel Xeon w7-2495X x 48. I haven't change any additional driver. Thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1019.20-oem 6.5.13 Uname: Linux 6.5.0-1019-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 17:28:14 2024 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33 InstallationDate: Installed on 2024-04-15 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2061585 Title: Everything laggy, file browsing in nautilus and terminal completion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969602] Re: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing
Sorry, didn't see the reply with the upstream link. It seems different to me, I haven't had any issues (that I've noticed) with invisible windows. I've attached a screen recording. In this, I have terminal in the foreground and alt-tab to settings. Because the mouse is outside the settings window (i.e., still over terminal), terminal gets pulled almost immediately to the front again. ** Attachment added: "video of the issue" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969602/+attachment/5594297/+files/Screencast%20from%2001-06-22%2012%3A19%3A59.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969602 Title: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976356] [NEW] "Dim screen" setting still operates when turned off
Public bug reported: I have "dim screen" set to off in my power settings, because it's mildly annoying when I'm on power, which is most of the time. Despite this, the screen will still dim after 30 seconds of inactivity. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-power-manager 3.32.0-2build2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 31 11:23:59 2022 InstallationDate: Installed on 2022-03-17 (74 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screenshot of the setting" https://bugs.launchpad.net/bugs/1976356/+attachment/5594063/+files/Screenshot%20from%202022-05-31%2011-24-57.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976356 Title: "Dim screen" setting still operates when turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1976356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974435] Re: wacom tablet button selection interface doesn't allow picking from dropdown
Someone else having the same issue, with workarounds: https://www.reddit.com/r/gnome/comments/tzbcru/gnome_42_wacom_cannot_set_tablet_buttons_actions/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974435 Title: wacom tablet button selection interface doesn't allow picking from dropdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1974435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974435] [NEW] wacom tablet button selection interface doesn't allow picking from dropdown
Public bug reported: I have a graphics table (Wacom Co., Ltd CTL-4100WL [Intuos BT (S)]), and gnome sees it happily. It provides me an interface to bind the buttons on the tablet to other functions, for example keyboard shortcuts. However it's not possible to select options in the dropdown for doing this, the mouse clicks are simply ignored on the dropdown. I also can't send a screenshot of the interface because prt scr doesn't work there, and when I use a different method I just get a black screenshot - so attached is a photo of the screen, sorry. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13.2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 13:42:02 2022 InstallationDate: Installed on 2022-03-23 (57 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) 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 jammy wayland-session ** Attachment added: "Photo of the interface that doesn't work" https://bugs.launchpad.net/bugs/1974435/+attachment/5591555/+files/PXL_20220520_114842609.MP.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974435 Title: wacom tablet button selection interface doesn't allow picking from dropdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1974435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973886] Re: "Install additional software" button does nothing
note: I apt installed gstreamer1.0-plugins-bad after trying the button, but before doing ubuntu-bug, hence it showing up in the GstreamerVersions.txt file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973886 Title: "Install additional software" button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1973886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973886] [NEW] "Install additional software" button does nothing
Public bug reported: I imported some m4a files, which by default can't be played. Rhythmbox gives me a button "Install Additional Software" to install the required codecs. Clicking this button does nothing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rhythmbox 3.4.4-5ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 11:06:03 2022 InstallationDate: Installed on 2022-03-17 (61 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screenshot showing the button in question" https://bugs.launchpad.net/bugs/1973886/+attachment/5590645/+files/Screenshot%20from%202022-05-18%2011-09-56.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973886 Title: "Install additional software" button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1973886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973463] Re: ZFS kernel null pointer dereference
Sorry, this is not a reliably reproducible bug so I won't be able to provide any more logs. Feel free to close if this this report is not useful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973463 Title: ZFS kernel null pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973463] Re: ZFS kernel null pointer dereference
** Package changed: ubuntu => zfs-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/1973463 Title: ZFS kernel null pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1973463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973463] [NEW] ZFS kernel null pointer dereference
Public bug reported: Ubuntu 22.04 LTS Linux server 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux zfs-2.1.2-1ubuntu3 zfs-kmod-2.1.2-1ubuntu3 [ 1249.508427] BUG: kernel NULL pointer dereference, address: 002a [ 1249.508435] #PF: supervisor read access in kernel mode [ 1249.508438] #PF: error_code(0x) - not-present page [ 1249.508440] PGD 0 P4D 0 [ 1249.508444] Oops: [#1] SMP NOPTI [ 1249.508447] CPU: 3 PID: 2119 Comm: txg_sync Tainted: PW O 5.15.0-30-generic #31-Ubuntu [ 1249.508452] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AB350M Pro4, BIOS P5.90 07/03/2019 [ 1249.508455] RIP: 0010:rw_owner+0x0/0x10 [zfs] [ 1249.508564] Code: 00 00 c3 0f 1f 80 00 00 00 00 65 48 8b 04 25 c0 fb 01 00 48 89 47 28 c3 66 90 48 c7 47 28 00 00 00 00 c3 0f 1f 80 00 00 00 00 <48> 8b 47 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e8 e7 [ 1249.508571] RSP: 0018:a8bec92b7c58 EFLAGS: 00010246 [ 1249.508576] RAX: RBX: 8cca7b162348 RCX: 0001 [ 1249.508580] RDX: RSI: c1494df0 RDI: 0002 [ 1249.508583] RBP: a8bec92b7c60 R08: 8cc62bfa4a80 R09: 8cc62bfa4a80 [ 1249.508587] R10: 8cc62bfa4a80 R11: R12: 8cca7b162280 [ 1249.508590] R13: 0009 R14: 8cca70f1ea30 R15: 8cc62bfa4a80 [ 1249.508594] FS: () GS:8ccdfeac() knlGS: [ 1249.508598] CS: 0010 DS: ES: CR0: 80050033 [ 1249.508601] CR2: 002a CR3: 0004c2b7e000 CR4: 003506e0 [ 1249.508607] Call Trace: [ 1249.508610] [ 1249.508613] ? RW_WRITE_HELD+0x9/0x20 [zfs] [ 1249.508689] dmu_buf_will_dirty_impl+0x87/0x110 [zfs] [ 1249.508786] dmu_buf_will_dirty+0x16/0x20 [zfs] [ 1249.508869] space_map_write+0x3f/0x1a0 [zfs] [ 1249.508970] metaslab_sync+0x60a/0x8b0 [zfs] [ 1249.509066] ? __raw_spin_unlock+0x9/0x10 [zfs] [ 1249.509182] vdev_sync+0x72/0x190 [zfs] [ 1249.509281] spa_sync_iterate_to_convergence+0x14f/0x1e0 [zfs] [ 1249.509388] spa_sync+0x2dc/0x5b0 [zfs] [ 1249.509483] txg_sync_thread+0x266/0x2f0 [zfs] [ 1249.509582] ? txg_dispatch_callbacks+0x100/0x100 [zfs] [ 1249.509683] thread_generic_wrapper+0x64/0x70 [spl] [ 1249.509695] ? __thread_exit+0x20/0x20 [spl] [ 1249.509704] kthread+0x12a/0x150 [ 1249.509708] ? set_kthread_struct+0x50/0x50 [ 1249.509712] ret_from_fork+0x22/0x30 [ 1249.509717] [ 1249.509718] Modules linked in: wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 libcurve25519_generic libchacha libblake2s_generic sctp ip6_udp_tunnel udp_tunnel macvtap macvlan vhost_net vhost vhost_iotlb tap xt_nat veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables libcrc32c nfnetlink bridge stp llc overlay intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd zfs(PO) zunicode(PO) snd_hda_codec_realtek kvm_amd zzstd(O) snd_hda_codec_generic zlua(O) snd_hda_codec_hdmi ledtrig_audio kvm crct10dif_pclmul ghash_clmulni_intel zcommon(PO) snd_usb_audio aesni_intel crypto_simd znvpair(PO) cryptd snd_usbmidi_lib zavl(PO) snd_hda_codec wmi_bmof snd_rawmidi rapl k10temp efi_pstore nls_iso8859_1 snd_hda_core snd_seq_device snd_hwdep icp(PO) mc snd_pcm spl(O) [ 1249.509765] input_leds snd_timer snd joydev soundcore ccp mac_hid sch_fq_codel nct6775 hwmon_vid parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid mpt3sas hid nvme uas raid_class usb_storage gpio_amdpt r8169 crc32_pclmul xhci_pci scsi_transport_sas ahci i2c_piix4 realtek e1000e nvme_core libahci xhci_pci_renesas wmi gpio_generic [last unloaded: snd_intel_sdw_acpi] [ 1249.509806] CR2: 002a [ 1249.509808] ---[ end trace 09588539e96f5ea2 ]--- [ 1250.063053] RIP: 0010:rw_owner+0x0/0x10 [zfs] [ 1250.063198] Code: 00 00 c3 0f 1f 80 00 00 00 00 65 48 8b 04 25 c0 fb 01 00 48 89 47 28 c3 66 90 48 c7 47 28 00 00 00 00 c3 0f 1f 80 00 00 00 00 <48> 8b 47 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e8 e7 [ 1250.063206] RSP: 0018:a8bec92b7c58 EFLAGS: 00010246 [ 1250.063211] RAX: RBX: 8cca7b162348 RCX: 0001 [ 1250.063215] RDX: RSI: c1494df0 RDI: 0002 [ 1250.063218] RBP: a8bec92b7c60 R08: 8cc62bfa4a80 R09: 8cc62bfa4a80 [ 1250.063222] R10: 8cc62bfa4a80 R11: R12: 8cca7b162280 [ 1250.063225] R13: 0009 R14: 8cca70f1ea30 R15: 8cc62bfa4a80 [ 1250.063229] FS: () GS:8ccdfeac() knlGS: [ 1250.063234] CS: 0010 DS: ES: CR0: 80050033 [ 1250.063237] CR2: 002a CR3: 0004c2b7e000 CR4: 003506e0 ** Affects: ubuntu Importance:
[Bug 1971624] [NEW] package memtest86+ 5.31b+dfsg-4 failed to install/upgrade: installed memtest86+ package post-installation script subprocess returned error exit status 64
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: memtest86+ 5.31b+dfsg-4 ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed May 4 21:55:37 2022 ErrorMessage: installed memtest86+ package post-installation script subprocess returned error exit status 64 InstallationDate: Installed on 2022-04-25 (9 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: grub2 Title: package memtest86+ 5.31b+dfsg-4 failed to install/upgrade: installed memtest86+ package post-installation script subprocess returned error exit status 64 UpgradeStatus: Upgraded to jammy on 2022-05-04 (0 days ago) modified.conffile..etc.grub.d.20_memtest86.: [deleted] ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971624 Title: package memtest86+ 5.31b+dfsg-4 failed to install/upgrade: installed memtest86+ package post-installation script subprocess returned error exit status 64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1971624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error
https://github.com/NVIDIA/egl-wayland/issues/41#issuecomment-959550980 and https://bugs.launchpad.net/egl-wayland/+bug/1968488 look related. ** Bug watch added: github.com/NVIDIA/egl-wayland/issues #41 https://github.com/NVIDIA/egl-wayland/issues/41 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969753] [NEW] gnome-power-statistics graph labels hard to read in dark mode
Public bug reported: I am running with Ubuntu set to dark mode. The graph labels on gnome- power-statistics are black on dark grey, which is very hard to read. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-power-manager 3.32.0-2build2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 11:20:41 2022 InstallationDate: Installed on 2022-03-17 (34 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "screenshot showing the problem" https://bugs.launchpad.net/bugs/1969753/+attachment/5582023/+files/Screenshot%20from%202022-04-21%2011-21-10.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969753 Title: gnome-power-statistics graph labels hard to read in dark mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1969753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969602] [NEW] gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing
Public bug reported: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969602 Title: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error
Oh wait, I'm being hit with Bug #1968929 where I now don't get wayland at all and so fell back to Xorg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error
After a recent update followed by a reboot, totem works again. Some mutter related updates were there, so you might well have been right about that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966790] Re: VLC doesn't produce audio
Started working again today, I guess something updated. ** Changed in: vlc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966790 Title: VLC doesn't produce audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1966790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966787] Re: Totem crashes on launch or when attempting to play video with a Wayland flush error
> 1. Tell us which message you now mean; and robin@malik:~/Videos$ totem Outrageous\ Fortune\ S04E08.m4v Gdk-Message: 11:02:22.100: Error flushing display: Protocol error robin@malik:~/Videos$ This result appears pretty much immediately, and no desktop window opens. > 2. Follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment No crash dump is produced as this isn't a SIGSEV or similar style crash, more a failing to work so shutting down abort. > Maybe related? This looks to me more like a screencast bug rather than a playback bug. Maybe relevant, I do get slightly different results sometimes. I just tried it again: robin@malik:~/Videos$ totem Outrageous\ Fortune\ S04E08.m4v (totem:3576): GStreamer-GL-CRITICAL **: 11:09:08.153: Failed to flush Wayland connection Gdk-Message: 11:09:08.153: Error flushing display: Protocol error (totem:3576): GStreamer-GL-CRITICAL **: 11:09:08.153: Failed to flush Wayland connection robin@malik:~/Videos$ i.e sometimes the "Failed to flush" message appears, sometimes it doesn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch or when attempting to play video with a Wayland flush error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966787] Re: Totem crashes on launch or when attempting to play video with a Wayland flush error
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch or when attempting to play video with a Wayland flush error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966790] [NEW] VLC doesn't produce audio
Public bug reported: If I attempt to play a file in VLC, it has no audio. The in-app volume is up, I have attempted changing the audio output from "automatic" to "Pulseaudio" with no change. Additionally, in the Ubuntu sound settings, where you can see a list of applications making sound and adjust their volume, it doesn't appear - suggesting to me that it's not talking to the sound system at all. It's perhaps notable that this same behaviour happens in both the apt and snap packages. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: vlc 3.0.16-1build7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 18:09:06 2022 InstallationDate: Installed on 2022-03-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vlc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966790 Title: VLC doesn't produce audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1966790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966790] Re: VLC doesn't produce audio
Additionally, sound in general works: I have rhythmbox playing right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966790 Title: VLC doesn't produce audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1966790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966787] Re: Totem crashes on launch
Update: my resolution didn't resolve it. If I attempt to play a file, it crashes with the same message as above. ** Summary changed: - Totem crashes on launch + Totem crashes on launch or when attempting to play video with a Wayland flush error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch or when attempting to play video with a Wayland flush error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966787] [NEW] Totem crashes on launch or when attempting to play video with a Wayland flush error
Public bug reported: If I launch totem, it crashes pretty much immediately. I resolved this by deleting .config/totem. I had moved some video files that had been previously opened within it recently, so possibly it was trying to reference them (for thumbnails or whatever) and that broke it. robin@malik:~$ totem (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection Gdk-Message: 18:00:17.844: Error flushing display: Protocol error robin@malik:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 18:00:39 2022 InstallationDate: Installed on 2022-03-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch or when attempting to play video with a Wayland flush error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966505] [NEW] Lock screen should listen for fingerprint immediately
Public bug reported: I have a laptop with a fingerprint reader that works fine. When the screensaver comes on, I can unlock one of two ways: 1) enter my password, 2) press a key and then press the fingerprint reader With 2) I'm required to press a key before the fingerprint reader starts listening. Instead, it should listen all the time so that I can just open the laptop to wake it from suspend, or if not suspended I can just press the fingerprint reader and have it unlock immediately. This way it'll behave more similar to how a phone's fingerprint reader does and save a (minor) unnecessary interaction. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 18:50:10 2022 InstallationDate: Installed on 2022-03-23 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966505 Title: Lock screen should listen for fingerprint immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1966505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu
This is reproducible in 22.04 also -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934579 Title: Nautilus crashes when opening places from the dock contextmenu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966067] [NEW] Snap application always asks for settings change on startup
Public bug reported: I use a snap application (youtube-music-desktop-app) that wants to handle a particular URL scheme. However, it asks this on every startup of the application, not remembering my selection in between launches. The message it gives is: Allow settings change? Allow snap "youtube-music-desktop-app" to change "default-url-scheme- handler" subproperty "ytmd" to "youtube-music-desktop-app_youtube-music- desktop-app.desktop"? This dialogue will close automatically after 5 minutes of inactivity. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.2+22.04 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 13:01:16 2022 InstallationDate: Installed on 2022-03-17 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "screenshot of dialogue box" https://bugs.launchpad.net/bugs/1966067/+attachment/5572162/+files/Screenshot-9.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966067 Title: Snap application always asks for settings change on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1966067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966054] [NEW] Dock gets confused in dual monitor setup with different scaling
Public bug reported: I have two monitors: the inbuilt laptop one, 1920x1080 at 125% scaling shifted slightly down to match the relative heights on my desk, and an external one, 1920x1080 at 100% scaling, primary. I have the dock set to autohide. When I open the dock by mousing to the side of the primary monitor it will appear, usually with the icons correct. Then, I think as a result of pushing the mouse slightly more to the left but not off the monitor (as the edge is slightly sticky), the icons will expand (see screenshot) I suspect as though they're picking up the scaling from the wrong monitor. Typically mousing over them will cause them to go back to their proper size again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 10:43:34 2022 InstallationDate: Installed on 2022-03-17 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "screenshot illustrating the incorrectly sized icons" https://bugs.launchpad.net/bugs/1966054/+attachment/5572135/+files/Screenshot-1-cropped.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966054 Title: Dock gets confused in dual monitor setup with different scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1966054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954746] Re: ASIX AX88179 compatible USB adapter not working
Arno, Hmm i have no problems regarding the visual part. That might be because i run a different version. Also i have no problems running a VPN. Currently i have 2 wireguards open and 1 openvpn. I think its time to bring in a maintainer for kernel modules. Now that we know that there need to be 2 kernel modules for the different disto's. Perhaps this can become a fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954746 Title: ASIX AX88179 compatible USB adapter not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954746] Re: ASIX AX88179 compatible USB adapter not working
I have added Kernel Packages team so they can take a look at it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954746 Title: ASIX AX88179 compatible USB adapter not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954746] Re: ASIX AX88179 compatible USB adapter not working
Hi Arno, please read comment number 5, i posted the answer there. You can swap out 'dev_get_tstats64' for 'usbnet_get_stats64' again (line 1030). the 'usbnet_get_stats64' had to be changed out for 21.10 but that might be different for 20.04. Just revert it back or or use the orignal tarball. comment 8 has the original firmware from the factory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954746 Title: ASIX AX88179 compatible USB adapter not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954746] Re: ASIX AX88179 compatible USB adapter not working
** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954746 Title: ASIX AX88179 compatible USB adapter not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954746] Re: ASIX AX88179 compatible USB adapter not working
I have also added the original tarball from the manufacturer if you want to do some clean work ** Attachment added: "Manufacturer original tarball" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954746/+attachment/5558863/+files/AX88179_178A_LINUX_DRIVER_v1.20.0_SOURCE.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954746 Title: ASIX AX88179 compatible USB adapter not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954746] Re: ASIX AX88179 compatible USB adapter not working
This xz contains the working files for the kernel module. Including the ax88179_178a.ko.orig as this is the original kernel driver that has been supplied with ubuntu 21.10. ax88179_178a.ko (148k) is the compiled kernel driver that I have compiled. ** Attachment added: "ax88179_178a kernel driver fix" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954746/+attachment/5558862/+files/ax88179_178a_firmware.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954746 Title: ASIX AX88179 compatible USB adapter not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954746] Re: ASIX AX88179 compatible USB adapter not working
I had similar problems with this too. The .ko that is delivered with 21.10 gives me the same output as above. I downloaded the firmware from ASIX and tried to compile it. That didn't work because 'usbnet_get_stats64' (line 1030) no longer exist in kernel 5.11 and up. I had to change it out for 'dev_get_tstats64' as this replaced a whole lot of statements. After this change it compiled perfectly and the USB3 adapter works just fine without error. I am running it right now and i got 0 drops in the last 4 hours. If needed i can add a .gz with my working files and compiled stuff. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954746 Title: ASIX AX88179 compatible USB adapter not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958184] [NEW] Display Configuration reset on every reboot
Public bug reported: I have three 4k displays. They are physically arranged as DP-2 DP-0 DP-1 Before I upgraded to Kubuntu 21.X, things worked fine: I once arranged the displays on the "Display Configuration" window and the setting was correctly restored. But once I updated to Kubuntu 21.X (originally from 19.10 I believe, then I used 20.04 and then upgraded to 21.X), this stopped working. The screen layout is reset on every reboot. The default layout is DP-0 DP-1 DP-2 which doesn't match the physical layout ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemsettings 4:5.22.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Jan 18 01:04:12 2022 ExecutablePath: /usr/bin/systemsettings5 InstallationDate: Installed on 2019-11-11 (798 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: systemsettings UpgradeStatus: Upgraded to impish on 2022-01-14 (3 days ago) ** Affects: systemsettings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958184 Title: Display Configuration reset on every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1958184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952661] [NEW] During install from live USB an error occurred at the end regarding the grub failure. This is a 4 OS system with XUbuntu being the 4th OS. I will find out if the OS installed witho
Public bug reported: Not certain if it is a bug. If the installer can look for Grub or other boot loaders and not try to install the GRUB bootloader, this could prevent this error. Not sure if this was the cause though. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 Date: Mon Nov 29 15:09:18 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed quiet splash --- LiveMediaBuild: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) 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.17 xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952661 Title: During install from live USB an error occurred at the end regarding the grub failure. This is a 4 OS system with XUbuntu being the 4th OS. I will find out if the OS installed without Grub. I may be able to get to it via grub customizer. I will try this as soon as I get out of this live session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1952661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
I Ctrl-F'ed for "snap" with no result so I assume it has not been mentioned: Running Ubuntu 21.04, I had Thunderbird with this bug. Removing it and installing it with snap fixed the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
To Snap and Ubuntu developers, here is a concrete example of why this is important and so many people are annoyed. Imagine a user likes to back up their home directory. (Imagine that! Crazy stuff!) The user will likely exclude hidden files from the backup, so as to avoid filling their storage with useless cruft, and maybe to avoid hitting storage or bandwidth limits (which can result in unexpected bills). By squatting the user's home directory, uninvited, Snap screws everything up. The user will need to hard-code an exception into the backup script. For one package. All the other packages respect the XDG rules. All of them except Snap. To Ubuntu developers in particular: by switching APT packages to Snap (Chromium for instance) and thereby causing an `apt install` to pull in Snap unrequested, you are breaking people's home directories, their scripts, their backup solutions, and the rules. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946714] [NEW] Unable to locally verify the issuer's authority.
Public bug reported: In a terminal, when I run the following: wget https://www.linz.govt.nz/sites/default/files/media/ntm/bsb/BSB_UPDATE.zip I get an error message about certificates, as follows. ERROR: cannot verify www.linz.govt.nz's certificate, issued by ‘CN=Thawte RSA CA 2018,OU=www.digicert.com,O=DigiCert Inc,C=US’: The file is not downloaded. I contacted the maintainers of the site, they declared there is no problem with the certificate. Of course, this probably isn't a problem with wget, or with curl which gives a similar error and the advice to go to this page: https://curl.se/docs/sslcerts.html Unfortunately that's way over my head, so I'm hoping someone helpful here can shed some light on the matter. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wget 1.20.3-1ubuntu1 Uname: Linux 5.14.11-051411-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Oct 12 19:19:54 2021 InstallationDate: Installed on 2019-05-26 (869 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: wget UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wget (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1946714 Title: Unable to locally verify the issuer's authority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1946714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
Will new media be available w/ this fix in place? I ask because running "dkms status" or any dkms command presently triggers this bug for me, and the only way forward I can see to being able to fix that system is new media w/ a patched kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886161] Re: Unattended upgrades should work on roaming laptops
@Julian Thanks for the explanation and the tip. Auto-retries would be a really beneficial feature but I get that you have a lot on your plate. Thanks for your work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: Unattended upgrades should work on roaming laptops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924256] [NEW] nvme unpredictibly disappears after some time
4_reserve_inode_write:5675: Journal has aborted avril 08 20:45:12 Auckland kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): mpage_map_and_submit_extent:2502: inode #12: comm kworker/u16:68: mark_inode_dirty error avril 08 20:45:12 Auckland kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): mpage_map_and_submit_extent:2504: comm kworker/u16:68: Failed to mark inode 12 dirty avril 08 20:45:12 Auckland kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): ext4_end_bio:345: I/O error 10 writing to inode 12 starting block 10107122) avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 1. avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 1158. avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 9366. avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 33554464. avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 33554465. ... ... ... There are 678 lines like this. I cut to make it readeable. ... ... avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 196084059. avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 196084060. avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 196084061. avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 196084062. avril 08 20:45:12 Auckland kernel: nvme nvme0: failed to set APST feature (-19) avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm pool: reading directory lblock 0 avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm pool: reading directory lblock 0 avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm pool: reading directory lblock 0 avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm pool-org.gnome.: reading directory lblock 0 avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm pool-org.gnome.: reading directory lblock 0 avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm pool-org.gnome.: reading directory lblock 0 avril 08 20:45:21 Auckland kernel: EXT4-fs warning: 21 callbacks suppressed avril 08 20:45:21 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm ls: error -5 reading directory block avril 08 20:45:24 Auckland kernel: EXT4-fs error: 3 callbacks suppressed avril 08 20:45:24 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm bash: reading directory lblock 0 avril 08 20:45:24 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm bash: reading directory lblock 0 avril 08 20:45:24 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm bash: reading directory lblock 0 avril 08 20:45:30 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm ls: error -5 reading directory block avril 08 20:45:47 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm pool-org.gnome.: error -5 reading directory block avril 08 20:46:30 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #54788097: comm codium: reading directory lblock 0 avril 08 20:46:30 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #54788097: comm codium: reading directory lblock 0 I think April, 8th is the last time I faced the problem. robin@
[Bug 1915824] [NEW] High CPU load from gnome-shell
Public bug reported: When doing nothing else, there is a constant base-line of CPU usage from gnome-shell: ``` op - 14:55:09 up 6 days, 1:39, 1 user, load average: 1.36, 1.52, 1.77 Tasks: 400 total, 3 running, 397 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 2.9 sy, 0.0 ni, 85.0 id, 0.1 wa, 0.0 hi, 2.6 si, 0.0 st MiB Mem : 31848.3 total, 4007.8 free, 12690.2 used, 15150.4 buff/cache MiB Swap:980.0 total,946.3 free, 33.7 used. 18037.0 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3236 myuser 20 0 5242476 902752 130032 R 41.9 2.8 278:24.48 gnome-shell ``` it is always burning one CPU somewhere between 30-60% Using strace for the process ID: ``` % time seconds usecs/call callserrors syscall -- --- --- - - 48.141.000284 1697706645150 stat 11.610.241121 3 62789 52442 recvmsg 8.630.179359 4 43747 poll 5.670.117864 2 44505 getpid 4.940.102593 2 44238 getdents64 4.330.089898 1 49124 22123 openat 4.160.086467 16 5215 ioctl 3.910.081323 5 14263 writev 2.110.043793 1 27259 close 1.680.034954 1 27001 fstat 1.150.023988 3 7035 sched_yield 1.100.022808 2 9373 read 0.780.016186 3 5119 write 0.520.010716 3 3541 189 futex 0.440.009226 2 4094 mprotect 0.330.006878 7 934 clock_nanosleep 0.320.006646 3 2018 mmap 0.170.003526 1 2040 munmap 0.000.10 012 getrusage 0.000.06 6 1 restart_syscall 0.000.04 0 5 recvfrom 0.000.00 0 2 lseek 0.000.00 0 3 timerfd_create 0.000.00 0 3 timerfd_settime -- --- --- - - 100.002.077650 1050027719904 total ``` What could be causing this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 16 14:50:18 2021 DisplayManager: lightdm InstallationDate: Installed on 2018-04-27 (1026 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2021-01-22 (25 days ago) ** Affects: gnome-shell (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/1915824 Title: High CPU load from gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886161] Re: Unattended upgrades should work on roaming laptops
Just an update, for what it's worth. I solved this problem with a shell script triggered by Network Manager's "up" hook. Because UU does not update the package list, I had to resort to a `apt-get update && apt-get dist-upgrade` with `DEBIAN_FRONTEND=noninteractive` and a whole bunch of options to make sure everything runs reliably in the background. Convoluted and laborious. But now my Ubuntu is *always* up to date. Before, it regularly went *months* without a security update. Putting aside whose fault it is, this absolutely IS a problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: Unattended upgrades should work on roaming laptops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886161] Re: Unattended upgrades should work on roaming laptops
** Summary changed: - UU should work on roaming laptops + Unattended upgrades should work on roaming laptops -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: Unattended upgrades should work on roaming laptops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826290] Re: geoclue mozilla location api key rate limited
@Sebastien Bacher Just doing an occasional Python GET request to the
same URL others are using:
https://location.services.mozilla.com/v1/geolocate?key=geoclue
Alternatively, calling that URL in a browser. It works occasionally, but
mostly it just returns a 403. The JSON string:
{"error":{"errors":[{"domain":"usageLimits","reason":"dailyLimitExceeded","message":"You
have exceeded your daily limit."}],"code":403,"message":"You have
exceeded your daily limit."}}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912916] [NEW] package libnvidia-compute-418-server (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340
Public bug reported: sudo dpkg --configure -a Setting up libaccinj64-10.1:amd64 (10.1.243-3) ... dpkg: dependency problems prevent configuration of libcuinj64-10.1:amd64: libcuinj64-10.1:amd64 depends on libcuda1 (>= 418.39) | libnvidia-tesla-cuda1 (>= 418.39) | libcuda.so.1 (>= 418.39) | libcuda-10.1-1; however: Package libcuda1 is not installed. Package libnvidia-compute-460:amd64 which provides libcuda1 is not installed. Package libnvidia-compute-455:amd64 which provides libcuda1 is not installed. Package libnvidia-tesla-cuda1 is not installed. Package libcuda.so.1 is not installed. Package libcuda-10.1-1 is not installed. Package libnvidia-compute-460:amd64 which provides libcuda-10.1-1 is not installed. Package libnvidia-compute-455:amd64 which provides libcuda-10.1-1 is not installed. dpkg: error processing package libcuinj64-10.1:amd64 (--configure): dependency problems - leaving unconfigured Setting up libthrust-dev (1.9.5-1) ... dpkg: dependency problems prevent configuration of libnvidia-ml-dev: libnvidia-ml-dev depends on libnvidia-ml1 (>= 418.39) | libnvidia-tesla-440-ml1 (>= 418.39) | libnvidia-tesla-418-ml1 (>= 418.39) | libnvidia-ml.so.1 (>= 418.39); however: Package libnvidia-ml1 is not installed. Package libnvidia-compute-460:amd64 which provides libnvidia-ml1 is not installed. Package libnvidia-compute-455:amd64 which provides libnvidia-ml1 is not installed. Package libnvidia-tesla-440-ml1 is not installed. Package libnvidia-tesla-418-ml1 is not installed. Package libnvidia-ml.so.1 is not installed. dpkg: error processing package libnvidia-ml-dev (--configure): dependency problems - leaving unconfigured Setting up libnppc10:amd64 (10.1.243-3) ... Setting up libnppial10:amd64 (10.1.243-3) ... Setting up libnvvm3:amd64 (10.1.243-3) ... Setting up libcusparse10:amd64 (10.1.243-3) ... Setting up libnvrtc10.1:amd64 (10.1.243-3) ... dpkg: dependency problems prevent configuration of nvidia-cuda-dev: nvidia-cuda-dev depends on libcuinj64-10.1 (= 10.1.243-3); however: Package libcuinj64-10.1:amd64 is not configured yet. nvidia-cuda-dev depends on libnvidia-ml-dev (= 10.1.243-3); however: Package libnvidia-ml-dev is not configured yet. dpkg: error processing package nvidia-cuda-dev (--configure): dependency problems - leaving unconfigured Setting up node-html5shiv (3.7.3+dfsg-3) ... Setting up libcupti-doc (10.1.243-3) ... Setting up libcupti10.1:amd64 (10.1.243-3) ... Setting up libnppisu10:amd64 (10.1.243-3) ... Setting up libnppicc10:amd64 (10.1.243-3) ... Setting up libncurses5:amd64 (6.2-0ubuntu2) ... Setting up libnppicom10:amd64 (10.1.243-3) ... dpkg: dependency problems prevent configuration of nvidia-profiler: nvidia-profiler depends on libcuinj64-10.1; however: Package libcuinj64-10.1:amd64 is not configured yet. dpkg: error processing package nvidia-profiler (--configure): dependency problems - leaving unconfigured Setting up libcusolver10:amd64 (10.1.243-3) ... Setting up libnvjpeg10:amd64 (10.1.243-3) ... dpkg: dependency problems prevent configuration of nvidia-cuda-toolkit: nvidia-cuda-toolkit depends on nvidia-profiler (= 10.1.243-3); however: Package nvidia-profiler is not configured yet. nvidia-cuda-toolkit depends on nvidia-cuda-dev (= 10.1.243-3); however: Package nvidia-cuda-dev is not configured yet. dpkg: error processing package nvidia-cuda-toolkit (--configure): dependency problems - leaving unconfigured Setting up libcublaslt10:amd64 (10.1.243-3) ... Setting up libcusolvermg10:amd64 (10.1.243-3) ... Setting up libnpps10:amd64 (10.1.243-3) ... Setting up nvidia-cuda-doc (10.1.243-3) ... Setting up opencl-c-headers (2.2~2019.08.06-g0d5f18c-1) ... Setting up ocl-icd-opencl-dev:amd64 (2.2.11-1ubuntu1) ... Setting up libcudart10.1:amd64 (10.1.243-3) ... Setting up libcufft10:amd64 (10.1.243-3) ... Setting up libnppim10:amd64 (10.1.243-3) ... Setting up libnppitc10:amd64 (10.1.243-3) ... Setting up libnppist10:amd64 (10.1.243-3) ... Setting up libvdpau-dev:amd64 (1.3-1ubuntu2) ... Setting up libnvtoolsext1:amd64 (10.1.243-3) ... Setting up libcurand10:amd64 (10.1.243-3) ... Setting up libnvgraph10:amd64 (10.1.243-3) ... Setting up libstdc++-8-dev:amd64 (8.4.0-3ubuntu2) ... Setting up libnppig10:amd64 (10.1.243-3) ... Setting up libnppidei10:amd64 (10.1.243-3) ... Setting up libnppif10:amd64 (10.1.243-3) ... Setting up libcufftw10:amd64 (10.1.243-3) ... Setting up nvidia-cuda-gdb (10.1.243-3) ... Setting up libcublas10:amd64 (10.1.243-3) ... Setting up libcupti-dev:amd64 (10.1.243-3) ... dpkg: dependency problems prevent configuration of nvidia-visual-profiler: nvidia-visual-profiler depends on nvidia-profiler (= 10.1.243-3); however: Package nvidia-profiler is not configured yet. dpkg: error processing package nvidia-visual-profiler (--configure): dependency problems - leaving unconfigured Setting up libnvblas10:amd64 (10.1.243-3) ... Setting up nvidia-opencl-dev:amd64 (10.1.243-3) ... Setting up g++-8
[Bug 1910811] [NEW] Video not playing correctly when scaling is 125%
Public bug reported: When I play video with scaling 100% it is working fine but when I increase scaling to 125% it corrupts the whole screen and show random glitches and black screens. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 01:05:19 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8329] Subsystem: Hewlett-Packard Company Radeon R7 M520 [103c:8329] InstallationDate: Installed on 2021-01-08 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5d5 Chicony Electronics Co., Ltd HP TrueVision HD Camera Bus 001 Device 002: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=a99d194c-5997-492d-818a-c6dc3589c1d4 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2019 dmi.bios.release: 15.52 dmi.bios.vendor: Insyde dmi.bios.version: F.52 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8329 dmi.board.vendor: HP dmi.board.version: 23.70 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.70 dmi.modalias: dmi:bvnInsyde:bvrF.52:bd03/04/2019:br15.52:efr23.70:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8329:rvr23.70:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 3FQ15PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910811 Title: Video not playing correctly when scaling is 125% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1910811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910401] Re: nvidia-kernel-source-440-server 440.95.01-0ubuntu0.20.04.1: nvidia kernel module failed to build
https://forums.developer.nvidia.com/t/linux-kernel-5-8-0-rc-3-1-breaks- nvidia-driver/140602 appears relevant. This claims to be fixed in the 450.57 driver release https://www.nvidia.com/download/driverResults.aspx/162107/en-us Attempting to switch to nvidia-driver-450-server via "Software & Updates" > "Additional Drivers" (for me) reported unmet dependencies for llvm10. Despite this, the driver change still appeared to run. It never declared completion, but having waited until nothing further appeared to be happening and rebooted, "Additional Drivers" reports that I am using the 450 driver, and this appears to have addressed the obvious symptoms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910401 Title: nvidia-kernel-source-440-server 440.95.01-0ubuntu0.20.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440-server/+bug/1910401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
I'm also on 20.04 and my network connection stopped working after an update today. I have a Broadcom BCM4360. I got things working again by following the steps shared by rafae-s (thank you!), but I expect that other 20.04 users will come across the same problem in the next couple of days. Does a fix for 20.04 also need to be released? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
If you like you can dowload the patched 5.10.3 kernel from the link i posted in #332. Just download the two files and install them via dpkg -i *.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@wangjun (biggerchina) i can confirm that #311 is working without any workarounds when applied on 5.10.3 with touchpad MSFT0001:00 04F3:3140 and Ubuntu 20.04, thanks! If anyone on a Debian based system is interested: i've uploaded the patched version as .deb-packages here https://drive.google.com/drive/folders/1ICZmuBx3ecwxtwufhSHbYmfnv9Prw- kc?usp=sharing @Coiby Xu (coiby) Phan Thanh Long (phanlong2811) any chance to get #311 backported to 5.10? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Had access to another Ideapad with touchpad MSFT0001:00 04F3:3140 installed. Kernel 5.10.2-051002-generic #202012210832 did not work out of the box but in combination with #322 it worked so i can confirm, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Piotr Tomaszewski (nfm886) according to #109 it seems like you have the "Elan" touchpad (mine is the "Synaptic" one) so it might behave a little different? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Piotr Tomaszewski (nfm886) can confirm my touchpad is the MSFT0001:00 06CB:7F28. I booted kernel 5.10.1 into recovery and then resumed regular boot and my touchpad works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Could you try to boot in recovery mode and then resume the normal boot process? I think i have the MSFT0001:00 06CB:7F28 touchpad installed but i'll check these days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Piotr Tomaszewski (nfm886) i just installed headers (all), image (generic) and modules (generic) from https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.10.1/amd64/ via 'dpkg -i *.deb', rebooted with new kernel 5.10.1 and everything worked. So no special config or parameter tweaking was necessary for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I'm on Ubuntu 20.04 with kernel 5.10.1 (https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.10.1/) and the touchpad is working on my Lenovo Legion 5. Thanks for that guys :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1100092] Re: Try to use a tempdir on same partition as source files
The temporary directory needs to be user settable. One size fits all is not working. Déjà-dup runs, and if the desktop is open at the time, a brief message is displayed. There may also be a desktop notification to be seen, but both of these are easily missed. There is no log file associated with the Déjà-dup control GUI. The control GUI does not note that any backups have failed. Effectively, backups fail silently. Should a new bug be raised for this silent failure? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1100092 Title: Try to use a tempdir on same partition as source files To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1100092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826290] Re: geoclue mozilla location api key rate limited
Update: key has not worked for several days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826290 Title: geoclue mozilla location api key rate limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907712] [NEW] grub installation crash
Public bug reported: the grub installation had crash, and I receive a message saying that the system will be able to boot. Actually, I'm writing in a window that automatically opened so, I don"t know what will happen when I will reboot. 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: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 10 21:39:45 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 (20200731) ProcEnviron: LANGUAGE=fr_FR.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.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/1907712 Title: grub installation crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1907712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826290] Re: geoclue mozilla location api key rate limited
Update: key is working again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826290 Title: geoclue mozilla location api key rate limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826290] Re: geoclue mozilla location api key rate limited
Can confirm that this stopped working 2 days ago. But when called manually from a script: https://location.services.mozilla.com/v1/geolocate?key=geoclue Can someone clarify: Is the shared "geoclue" key likely to come to life again, and if so is there any timeline? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826290 Title: geoclue mozilla location api key rate limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903473] Re: Bluetooth does not work
For me it's a dongle (https://www.amazon.de/Mpow-Bluetooth-Empf%C3 %A4nger-Lautsprecher- kompatibel/dp/B087JRFGV7?pd_rd_w=YmEc6_rd_p=8d2a1a06-f0ba-4603-bd06-75edf607bd62_rd_r=7PQ125F33S6FJFDZX9SK_rd_r =4484adca-29c6-4c15-b00d- b94cc61893bb_rd_wg=rSu7g_rd_i=B087JRFGV7_=pd_bap_m_rp_1_sc) and it's always plugged in pre-boot. Also removing and plugging it in again doesn't help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903473 Title: Bluetooth does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788154] Re: Update jsvc to support Java 9+
Still old version in the archive for Ubuntu 20.04. Any plans to solve this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788154 Title: Update jsvc to support Java 9+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/commons-daemon/+bug/1788154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886161] Re: UU should work on roaming laptops
@rbalint As I detailed, the problems cannot *all* be resolved by config. The biggest one, the first above, is still there. If you turn on a laptop when (1) an update is overdue and (2) there is not yet an internet connection, then the update will not run even if the connection becomes available 5 minutes later. This is an **absolutely typical** situation when on the go and connecting to new wifi networks. Perhaps this is anacron's fault, or systemd's or something, I am not sure. What is certain is that, in the real world, in this common situation, unattended upgrades does not upgrade Ubuntu unattended. I believe that is a significant problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: UU should work on roaming laptops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1886161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
>At this point you are the one ignoring what others are saying. Come on @niemeyer, no point throwing fuel on the fire. YOU guys screwed up bad with this. You have never really admitted that, just promised to fix it. WE are whining about it annoyingly. We have made our point and should stop. There. Everyone is wrong. End of discussion until there is new information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
@avamander If you read carefully the discussion above you will see that the "resistance" has crumbled, this now seems to be a priority bug which will be fixed fairly soon. The Snap team made a bad design mistake which is harder to fix than it looks, see posts by @zyga for detail. Nobody "wants to piss off" anyone, that is silly. Most of us here are not paying customers, perhaps it would be good that we remember that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
@niemeyer Your tone suggests that you do not understand why this seemingly small issue is so important to many people. It is NOT just esthetics, or rigid ideology. Others have mentioned issues with mounts and disk space. Or imagine having a script which follows the XDG spec, for backing up or syncing one's personal data or something similar. When Snap, which is now built into Ubuntu, comes out of nowhere and dumps large quantities of data, that will certainly require rewriting the script and may even have cost money if you were on a metered connection. This is wny, yes, I literally preferred purging Snap and resorting to jiggery-pokery by pinning a Debian APT repo just to get Chromium. So my comment was really in response to a remark by @stolowski that "our hands are full with other features, and of higher priority". Tell us at least, are there any other bugs that have as many users whining as this one? Perhaps the actual users should have a little more say in deciding priority. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
Egregious violation of the XDG specification, almost a thousand users actively complaining, years of stalling, and still Snap managers are explicitly saying that this bug is not a priority. You have to ask what they think IS important, or whether they care about their users at all. @zyga seems well-meaning, but still, the fact that this is difficult to fix is on Snap, no one else. It is the predictable result of a terrible design decision made by Snap early on. Time to quit stalling and call this bug a priority at last. Until it is fixed I have to purge Snap, no choice, like so many others here. What a silly situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886161] Re: UU should work on roaming laptops
** Summary changed: - UU is almost useless on itinerant laptops + UU should work on roaming laptops -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: UU should work on roaming laptops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1886161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886161] [NEW] UU is almost useless on itinerant laptops
Public bug reported: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. ** Affects: unattended-upgrades (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/1886161 Title: UU is almost useless on itinerant laptops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1886161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879377] Re: network-manager-fortisslvpn not working but openfortivpn does
** Description changed: - I've used network-manager-fortisslvpn to stablish a VPN but it doesen't work. I setup the VPN and then try to load a web page which acn only be loaded if on the VPN. The window keeps still trying to connect (dots indicating loading keep moving) - I do it directly from a terminal, via openfortivpn, i.e. I run the command - openfortivpn the.apropriate.url:port -u my.user - and it establishes the tunnel ok. I'm able to load the said page right away. + I've used network-manager-fortisslvpn to establish a VPN but it doesn't work. I setup the VPN and then try to load a web page which can only be loaded if on the VPN. The window keeps still trying to connect (dots indicating loading keep moving) + I do it directly from a terminal, via openfortivpn, i.e. I run the command + openfortivpn the.apropriate.url:port -u my.user + and it establishes the tunnel OK. I'm able to load the said page right away. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager-fortisslvpn 1.2.10-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 20:12:58 2020 InstallationDate: Installed on 2020-04-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: network-manager-fortisslvpn UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879377 Title: network-manager-fortisslvpn not working but openfortivpn does To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-fortisslvpn/+bug/1879377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882112] Re: [radeon] Screen freeze
UPDATE: 11h41GMT Fri 12 Jun 2020 Rob Jarvis: Freeze occured again today, second time since original report. This time I was able to Alt+F2 and switch into the desktop in focus in the 4-part desktop 'palette' view. This killed the freeze. The freeze seems to be associated with 2 factors which may be related, or not: 1) a having desktop with windows which overlap out of the visible area. When swithcing into dektop palette mode the previously out of sight bits of the windows in the one desktop then show as overlapping into the adjacent desktops in the palette view (clearly all 4 are mapped into the same large pixel space). If I try to tidy up the overlaps in the palette view I am likely to hit a freeze. If I return to the single desktop and tidy up the windows by reducing their size and ensure all fit into the active desktop, then return to the palette view, I can then shuffle the smaller windows from one desktop to another without hitting a freeze, unless... 2)... I drag a window diagonally, say from Top-left to bottom right, so that the subject window traverses more than 2 desktop areas. Then I am more leikely to see the freeze... it seems. If I drag a desktop completely from that top left to top right and then wholly from there to bottom right it seems to stay well behaved and doesn't freeze.. so far. ==> END OF UPDATE 11h41GMT Fri 12 Jun 2020 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882112 Title: [radeon] Screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1882112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882112] Re: [radeon] Screen freeze
.. just in case it is relevant... my display is a bit of an anachronism. It is a old wide-screen AOC F22+ LCD Monitor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882112 Title: [radeon] Screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1882112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882112] Re: [radeon] Screen freeze
The system 'hung' on me again. Active cursor etc. but I didn't explore for fear of changing any status data.. just hit the button and rebooted after attempting PrtScrn [but can't find where that image got written]. Ran journalctl -b-1 > prevboot.txt which is attached here. I was in the 4-way split desktop. Only 1 was active this time. It had 2 windows open in it. 1 was overlapping its desktop area (top-left) into the next below it. As i dragged that window down into the bottom left desktop area the system froze. No contention for resources apparent this time. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1882112/+attachment/5381996/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882112 Title: [radeon] Screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1882112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882112] [NEW] Xorg freeze
Public bug reported: This may be correlated to the move to Bionic Beaver(?) LTS, now 18.04.4. It may also be correlated to getting low on disk space on my system drive (50GB SSD) and putting pressure on swap space. e.g when system HDD <= 1GB. My secondary HDD is a 1TB USB spinning device that sometimes seems to go into sleep mode and then fails to rapidly respond to IO request or may be is in a 'hot IO' state. On my Bus I have a low capacity HDD that is essentially unused because it rarely comes ready when I boot. If it is partially alive it is conceivable that it might be chattering and so competing for IO interrupt handling bandwidth? The problem only occurs when I have selected the desktop management tile from the 'side tray' and if I then shuffle or better align the windows inside one of the four desktops so as to stop them running into the neighbouring desktop area. Particularly, it seems to me, when at least one of the desktops is quite busy with windows open in it and the overlapped desktop has a few also. The fewer windows in total across the desktops the less likely it seems that rearranging a few will have any bad effect. When the freeze occurs then 60%(?) of the time it ends in a 'big red switch' reboot. The cursor stays active but ineffective. Keyboard combinations, like Alt+W, will sometimes succeed in bringing up to full screen mode and active the desktop that was in focus and constitutes a recovery. Other times, and keys, will delete focussed windows in the focussed desktop, and Tab will move focus around the 4 desktops. SHIFT+Print Screen also executes but just takes the whole screen and dumps it somewhere I haven't yet located... with sound effect. Hope this helps... I am not at fully at home with Ubuntu/Linux yet... having spent a lifetime on glasshouse legacy IBM mainframe field systems engineering. I am making myself more system disk space meanwhile, and while extract my old Maxtor. It would be nice if I didn't have to up my system disk to hundreds of GB! best regards, Rob ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Jun 4 11:31:56 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: I don't know GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] [1002:9993] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7480D] [1043:8526] InstallationDate: Installed on 2016-11-27 (1284 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=1d959d4a-ac83-43a5-8c0f-a6956d68c1f8 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A55BM-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd10/10/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA55BM-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Aug 18 06:53:30 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags:
[Bug 1879377] [NEW] network-manager-fortisslvpn not working but openfortivpn does
Public bug reported: I've used network-manager-fortisslvpn to stablish a VPN but it doesen't work. I setup the VPN and then try to load a web page which acn only be loaded if on the VPN. The window keeps still trying to connect (dots indicating loading keep moving) I do it directly from a terminal, via openfortivpn, i.e. I run the command openfortivpn the.apropriate.url:port -u my.user and it establishes the tunnel ok. I'm able to load the said page right away. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager-fortisslvpn 1.2.10-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 20:12:58 2020 InstallationDate: Installed on 2020-04-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: network-manager-fortisslvpn UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager-fortisslvpn (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/1879377 Title: network-manager-fortisslvpn not working but openfortivpn does To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-fortisslvpn/+bug/1879377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
So, it seems really working. Thank you so much Christian! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
So, I just rebooted and it seems fine. Puting in /etc/modules the line "kvm_amd" worked and I can start VM without restarting libvirt. So far said. So, what's up with that now? Is that bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
Hi. Under libvirt there are actually 2 processes: qemu-system-x86_64 -enable-kvm -S -no-user-config -nodefaults -nographic -machine none,accel=kvm:tcg -qmp unix:/var/lib/libvirt/qemu/qmp- 2NL5J0/qmp.monitor,server,nowait -pidfile /var/lib/libvirt/qemu/qmp- 2NL5J0 qemu-system-x86_64 -enable-kvm -S -no-user-config -nodefaults -nographic -machine none,accel=kvm:tcg -qmp unix:/var/lib/libvirt/qemu/qmp- 2NL5J0/qmp.monitor,server,nowait -pidfile /var/lib/libvirt/qemu/qmp- 2NL5J0/qmp.pid -daemonize -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
I did some tries as complete reinstall but it's still occcuring and now I'm also sure it stops system for proper shutdown. 2.1 $ virsh list --all is hanging 2.2 $ systemctl status libvirtd.service libvirtd-admin.socket libvirtd-ro.socket libvirtd.socket Report as attachment. ** Attachment added: "log1_systemctl status" https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1876266/+attachment/5368499/+files/log1_systemctl%20status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
2.2 $ cat /var/log/libvirtd.log As attachment ** Attachment added: "libvirtd.log" https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1876266/+attachment/5368500/+files/libvirtd.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
Third - does adding a new connection in virt-manager get it done as well? Via "File" -> "Add connection" I just tried this and it stucks on loading pointer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
Hi, I wasn't working recently. Yes, I restart quite regularly. What's the issue is that is is likely correlated with me unable to shutdown the system too. It hangs on and doesn't turn off even after 90s. I have to do hardreset. $ virsh list --all- is hanging on...as you predicted I posted all those logs after I boot up and uploaded to G Drive: https://drive.google.com/drive/folders/1MEc7-fq89JdujZInHuhxY451GvM-qZhp?usp=sharing Thanks you guys for helping me! Robin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875985] Re: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4
Bug confirmed for another Inspiron 13-5368. Under kernel 4.15.0-99 & Ubuntu 18.04.4 & Gnome desktop, there is no sound from internal speaker or on headphone jack, and also no microphone input signal. Other outputs (HDMI & BlueTooth) still work Previous kernel (4.15.0-96) works as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875985 Title: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875215] [NEW] deja-dup 40.6 error on 20.04 _clock_nanosleep
Public bug reported: Deja-dup error when trying to make a backup Description:Ubuntu 20.04 LTS Release:20.04 deja-dup 40.6 ERROR: BackendException: Could not initialize backend: /snap/core18/current/lib/x86_64-linux-gnu/librt.so.1: undefined symbol: __clock_nanosleep, version GLIBC_PRIVATE ** Affects: deja-dup (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/1875215 Title: deja-dup 40.6 error on 20.04 _clock_nanosleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1875215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873050] [NEW] Link creation property of file manager off by default
Public bug reported: Hello, Summary describes everything. This is a very useful feature and a lot more intuitive than typing ln -s Why is it off by default? Kind Regards Robin Müller ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 19:50:25 2020 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: feature-request -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873050 Title: Link creation property of file manager off by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
I agree with everything stated in comment #2 except that it's not 2017, *It's 2020, come on.* Call me a superficial but I enjoy a nice and tidy home folder and this is the only reason why I go for the repos (currently on Void Linux) or in certain cases flatpaks over snaps. I would love to go for snaps. Just listened to episode 2 of season 13 of the Ubuntu Podcast where Popey had packaged up "ncspot" into a snap. I go to the ncspot github page and try installing it with cargo, the rust package thing and it fails with horrible error messages - no ncspot for me then. Who do I pay and how much does the person in charge/responsible want to fix this? People all-over the planet will rejoice when this gets fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787031] Re: installing thinkfan package does not make thinkfan usable
I installed thinkfan too, no change. I tried $ systemctl status thinkfan.service and got: ● thinkfan.service - simple and lightweight fan control program Loaded: loaded (/lib/systemd/system/thinkfan.service; disabled; vendor preset: enabled) Active: inactive (dead) so I restarted the service then checked the status and got: ● thinkfan.service - simple and lightweight fan control program Loaded: loaded (/lib/systemd/system/thinkfan.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-04-03 20:37:52 NZDT; 3s ago Process: 6662 ExecStart=/usr/sbin/thinkfan $DAEMON_ARGS (code=exited, status=4) Apr 03 20:37:52 darwin systemd[1]: thinkfan.service: Control process exited, code=exited status=4 Apr 03 20:37:52 darwin thinkfan[6662]: WARNING: Using default temperature inputs in /proc/acpi/ibm/thermal. Apr 03 20:37:52 darwin systemd[1]: thinkfan.service: Failed with result 'exit-code'. Apr 03 20:37:52 darwin thinkfan[6662]: /proc/acpi/ibm/thermal: No such file or directory Apr 03 20:37:52 darwin thinkfan[6662]: add_sensor: Error getting temperature. Apr 03 20:37:52 darwin thinkfan[6662]: /proc/acpi/ibm/thermal: No such file or directory Apr 03 20:37:52 darwin thinkfan[6662]: Error parsing temperatures: Apr 03 20:37:52 darwin thinkfan[6662]: readconfig: Error getting temperature. Apr 03 20:37:52 darwin systemd[1]: Failed to start simple and lightweight fan control program. Apr 03 20:37:52 darwin thinkfan[6662]: Refusing to run without usable config file! Looking in /proc/acpi/ibm/ , there is no "thermal" node. ubuntu 18.04.4, thinkpad t420 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787031 Title: installing thinkfan package does not make thinkfan usable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thinkfan/+bug/787031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870451] Re: I accepted SW update and now doesnt exit sleep
Additional note The main screen with a TIME clock on it appears but it dosent respond to any key presses or the mouse so dont get logon prompt etc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870451 Title: I accepted SW update and now doesnt exit sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870451] [NEW] I accepted SW update and now doesnt exit sleep
Public bug reported: I very recently accepted a SW update from Ubuntu after that when my laptop goes to sleep i cant wake it , i have to power cycle.. This was working before the update. HP ELiteBook 8440p Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-91-generic 4.15.0-91.92 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robin 1736 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:01:25 2020 InstallationDate: Installed on 2018-10-11 (539 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=ac0d7bbe-3453-4b2e-ad03-06d82cda4739 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-91-generic N/A linux-backports-modules-4.15.0-91-generic N/A linux-firmware 1.173.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.11 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.31 dmi.chassis.asset.tag: AG021536 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.11:bd11/25/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870451 Title: I accepted SW update and now doesnt exit sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848018] Re: [solved] PXE boot/nfsboot broken; Eoan Ermine; 19.10
I also had this problem and indeed, the solution was ip=dhcp. 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/1848018 Title: [solved] PXE boot/nfsboot broken; Eoan Ermine; 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1848018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1342429] Re: ubuntu-bug crashes when there's no sources.list
This is still a bug in a supported version. robin@taniwha:/etc/apt$ sudo mv sources.list sources.list.bak [sudo] wachtwoord voor robin: robin@taniwha:/etc/apt$ ubuntu-bug apport Gtk-Message: 11:56:56.196: GtkDialog mapped without a transient parent. This is discouraged. [... displays the message in the attached screenshot ...] robin@taniwha:/etc/apt$ sudo mv sources.list.bak sources.list robin@taniwha:/etc/apt$ ubuntu-bug apport [... proceeds to collect data like normal ...] robin@taniwha:/etc/apt$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic ** Attachment added: "Selectie_417.png" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1342429/+attachment/5334264/+files/Selectie_417.png ** Changed in: apport (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1342429 Title: ubuntu-bug crashes when there's no sources.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1342429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865046] [NEW] Gimp Crashing everytime I copy, I uninstalled qlipper but it made no difference si I reinstalled it.
Public bug reported: I have just upgraded from 18.4 to 19.10 and had trouble with the wallpaper so reinstalled OS & now I have this crashing Gimp thing.It is not relater to the Clipboard manager because I tried it without that and the symptoms were the same. ** Affects: gimp (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/1865046 Title: Gimp Crashing everytime I copy, I uninstalled qlipper but it made no difference si I reinstalled it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1865046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)
Same problem with Ubuntu 19.10 running in VMware Workstation 15.5.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825842 Title: [vmware] Background goes white when using scaling (200%, 300% or 400%) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613793] Re: o2cb stopping Failed
In an OCFS2 cluster of XenServer 7.1.1 hosts, we met the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/613793 Title: o2cb stopping Failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/613793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665151] Re: Apache ignores disable TLSv1.0
I had the same problem - had! It turns out, that the SSLCipherSuite list on the default vHopst (as reported of apachectl -D DUMP_VHOSTS) has to be capable of TLSv1.1 ciphers. It is also needed, that the default vHost has TLSv1.1 enabled in order to use that on other vHosts. So, the default vHost is the key here. I cant believe that this should be correct. If I dont want to enable TLSv1.1 on the default but on the 3rd vHost, this must be working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665151 Title: Apache ignores disable TLSv1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1665151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
