[Bug 2067443] [NEW] Several apparmor profiles fail to enable after upgrading to noble
Public bug reported:
I started investigating why after upgrading to noble Brave (the browser)
won't start. Noticed something is wrong with apparmor:
# aa-enforce brave
ERROR: Can't parse mount rule mount options=(rw, make-slave) -> **,
This makes no sense because the profile doesn't contain almost anything:
# This profile allows everything and only exists to give the
# application a name instead of having the label "unconfined"
abi ,
include
profile brave /opt/brave.com/brave/brave flags=(unconfined) {
userns,
# Site-specific additions and overrides. See local/README for details.
include if exists
}
Brave needs only the userns, the rest of the rules are irrelevant.
Verified this by sudo sysctl -w
kernel.apparmor_restrict_unprivileged_userns=0, which fixed that issue
as an ugly hack.
Then I started looking at what aa-status tells me, and the amount of
loaded/enforced profiles looks incorrect:
35 profiles are loaded.
33 profiles are in enforce mode.
I think there were 70+ loaded and enforced profiles before the system
upgrade. The profile files seem to be around, but they just don't work.
Apparently many profiles don't load because of the mount rule issue?
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: apparmor 4.0.0-beta3-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed May 29 06:42:47 2024
InstallationDate: Installed on 2021-08-02 (1030 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic
root=UUID=9d876767-ca94-4fa2-9a12-ece62ac1141d ro quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog:
2024-05-29T06:11:06.594368+03:00 nuc dbus-daemon[1087]: [system] AppArmor
D-Bus mediation is enabled
2024-05-29T06:11:09.222685+03:00 nuc dbus-daemon[1809]: [session uid=140
pid=1809] AppArmor D-Bus mediation is enabled
2024-05-29T06:11:29.141193+03:00 nuc dbus-daemon[2628]: [session uid=1000
pid=2628] AppArmor D-Bus mediation is enabled
UpgradeStatus: Upgraded to noble on 2024-05-29 (0 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2024-03-30T10:43:24.749002
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067443
Title:
Several apparmor profiles fail to enable after upgrading to noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2067443/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
I'm seeing the same problem on Ubuntu 22.04.4 LTS: $ ps -eHo pid,ppid,etimes,command | grep -w [a]pt 3162391 1 3033258 /bin/sh /usr/lib/apt/apt.systemd.daily update 3162395 3162391 3033258 /bin/sh /usr/lib/apt/apt.systemd.daily lock_is_held update 3162423 3162395 3033257 apt-get -qq -y update 3162432 3162423 3033257 /usr/lib/apt/methods/http 3163221 3162423 3033222 /usr/lib/apt/methods/gpgv And since /usr/lib/apt/apt.systemd.daily is from package apt, this is definitely a bug in apt. A pretty simple workaround would be to run /usr/bin/timeout 15m /usr/lib/apt/apt.systemd.daily lock_is_held update instead. Of course, that wouldn't fix the underlying problem but it would automatically release the lock after 15 minute delay. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2003851 Title: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
This sounds like a race condition that leads to live lock, considering that both gpgv and apt are waiting for the other end to speak at the same time. I assume the protocol between these is custom made for this connection. How the protocol is supposed to prevent this live lock situation from happening? If the protocol cannot avoid this situation, then the bug is in the protocol design and the least invasive fix is to add timeout for the waiting time and consider the execution as failed if timeout is triggered. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2003851 Title: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058824] Re: nvidia-driver-545 (and version 550) randomly hangs with compositing manager on VT change
Here's driver parameters (should be all defaults): # grep . /sys/module/nvidia*/parameters/* /sys/module/nvidia_drm/parameters/fbdev:N /sys/module/nvidia_drm/parameters/modeset:Y /sys/module/nvidia_modeset/parameters/config_file:(null) /sys/module/nvidia_modeset/parameters/disable_hdmi_frl:N /sys/module/nvidia_modeset/parameters/disable_vrr_memclk_switch:N /sys/module/nvidia_modeset/parameters/fail_malloc:-1 /sys/module/nvidia_modeset/parameters/hdmi_deepcolor:N /sys/module/nvidia_modeset/parameters/malloc_verbose:N /sys/module/nvidia_modeset/parameters/opportunistic_display_sync:Y /sys/module/nvidia_modeset/parameters/output_rounding_fix:Y /sys/module/nvidia_modeset/parameters/vblank_sem_control:N /sys/module/nvidia_uvm/parameters/uvm_ats_mode:1 /sys/module/nvidia_uvm/parameters/uvm_block_cpu_to_cpu_copy_with_ce:0 /sys/module/nvidia_uvm/parameters/uvm_channel_gpfifo_loc:auto /sys/module/nvidia_uvm/parameters/uvm_channel_gpput_loc:auto /sys/module/nvidia_uvm/parameters/uvm_channel_num_gpfifo_entries:1024 /sys/module/nvidia_uvm/parameters/uvm_channel_pushbuffer_loc:auto /sys/module/nvidia_uvm/parameters/uvm_conf_computing_channel_iv_rotation_limit:2147483648 /sys/module/nvidia_uvm/parameters/uvm_cpu_chunk_allocation_sizes:2166784 /sys/module/nvidia_uvm/parameters/uvm_debug_enable_push_acquire_info:0 /sys/module/nvidia_uvm/parameters/uvm_debug_enable_push_desc:0 /sys/module/nvidia_uvm/parameters/uvm_debug_prints:0 /sys/module/nvidia_uvm/parameters/uvm_disable_hmm:N /sys/module/nvidia_uvm/parameters/uvm_downgrade_force_membar_sys:1 /sys/module/nvidia_uvm/parameters/uvm_enable_builtin_tests:0 /sys/module/nvidia_uvm/parameters/uvm_enable_debug_procfs:0 /sys/module/nvidia_uvm/parameters/uvm_enable_va_space_mm:1 /sys/module/nvidia_uvm/parameters/uvm_exp_gpu_cache_peermem:0 /sys/module/nvidia_uvm/parameters/uvm_exp_gpu_cache_sysmem:0 /sys/module/nvidia_uvm/parameters/uvm_fault_force_sysmem:0 /sys/module/nvidia_uvm/parameters/uvm_force_prefetch_fault_support:0 /sys/module/nvidia_uvm/parameters/uvm_global_oversubscription:1 /sys/module/nvidia_uvm/parameters/uvm_leak_checker:0 /sys/module/nvidia_uvm/parameters/uvm_page_table_location:(null) /sys/module/nvidia_uvm/parameters/uvm_peer_copy:phys /sys/module/nvidia_uvm/parameters/uvm_perf_access_counter_batch_count:256 /sys/module/nvidia_uvm/parameters/uvm_perf_access_counter_mimc_migration_enable:-1 /sys/module/nvidia_uvm/parameters/uvm_perf_access_counter_momc_migration_enable:-1 /sys/module/nvidia_uvm/parameters/uvm_perf_access_counter_threshold:256 /sys/module/nvidia_uvm/parameters/uvm_perf_fault_batch_count:256 /sys/module/nvidia_uvm/parameters/uvm_perf_fault_coalesce:1 /sys/module/nvidia_uvm/parameters/uvm_perf_fault_max_batches_per_service:20 /sys/module/nvidia_uvm/parameters/uvm_perf_fault_max_throttle_per_service:5 /sys/module/nvidia_uvm/parameters/uvm_perf_fault_replay_policy:2 /sys/module/nvidia_uvm/parameters/uvm_perf_fault_replay_update_put_ratio:50 /sys/module/nvidia_uvm/parameters/uvm_perf_map_remote_on_eviction:1 /sys/module/nvidia_uvm/parameters/uvm_perf_map_remote_on_native_atomics_fault:0 /sys/module/nvidia_uvm/parameters/uvm_perf_migrate_cpu_preunmap_block_order:2 /sys/module/nvidia_uvm/parameters/uvm_perf_migrate_cpu_preunmap_enable:1 /sys/module/nvidia_uvm/parameters/uvm_perf_pma_batch_nonpinned_order:6 /sys/module/nvidia_uvm/parameters/uvm_perf_prefetch_enable:1 /sys/module/nvidia_uvm/parameters/uvm_perf_prefetch_min_faults:1 /sys/module/nvidia_uvm/parameters/uvm_perf_prefetch_threshold:51 /sys/module/nvidia_uvm/parameters/uvm_perf_reenable_prefetch_faults_lapse_msec:1000 /sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_enable:1 /sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_epoch:2000 /sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_lapse_usec:500 /sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_max_resets:4 /sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_nap:1 /sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_pin:300 /sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_pin_threshold:10 /sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_threshold:3 /sys/module/nvidia_uvm/parameters/uvm_release_asserts:1 /sys/module/nvidia_uvm/parameters/uvm_release_asserts_dump_stack:0 /sys/module/nvidia_uvm/parameters/uvm_release_asserts_set_global_error:0 And I'm using displayport connector in case that makes a difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058824 Title: nvidia-driver-545 (and version 550) randomly hangs with compositing manager on VT change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2058824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058824] [NEW] nvidia-driver-545 (and version 550) randomly hangs with compositing manager on VT change
Public bug reported: This issue doesn't happen with Nnvidia version 525 or 535 but it happens with 545 and 550. Steps to reproduce: - Run window manager or desktop environment without compositor manager. For example XFCE with Settings – Window Manager Tweaks – Compositor and disable Enable display compositing. (The problem is visible with this compositor, too, but getting out of hang with this one is harder.) - The problem seems to be some kind of race condition because in "only" happens about 70% of the time for me. I'm using package "linux-tools- lowlatency-hwe-22.04" to get kernel with PREEMPT_DYNAMIC which may trigger the race condition easier. - Run picom as follows to make sure it has no config of any kind that might avoid the problem: picom --config /dev/null --show-all-xerrors --log-level=TRACE & sleep 20; killall picom Note that this will emit a lot of log messages and picom will be killed after 20 seconds (resulting in no compositor X session which should be usable if not pretty). - Switch to different virtual terminals with CTRL+ALT+F1, CTRL+ALT+F2, ..., CTRL+ALT+F7 and wait for display to refresh on each terminal. - Assuming your initial virtual terminal was VT 7 as usual for GUI desktop, you should now see fully black screen with your usual mouse cursor only. Wait for the sleep timer above (20 seconds) to go off and kill picom to restore your screen. If you had compositing enabled in XFCE Window manager, you would be seeing the same issue but getting out of this issue is much harder because XFCE window manager implements the compositing internally and having compositing hang you would have to kill your window manager to get rid of it! I'm assuming this also happens with other software, too, that simply happens to trigger the racy codepath during VT switch but the above is the best way to reproduce the issue at will. The problem happens pretty often rapidly changing to VT 1 and back to VT 7, too. It may be faster way to reproduce the problem. When picom hangs, the last line it outputs to stderr is as follows: [ 2024-03-23 22:24:17.069 draw_callback_impl TRACE ] Render start, frame 416 Normally this should be followed by [ 2024-03-23 22:24:17.069 draw_callback_impl TRACE ] Render end on the same millisecond or one later but when NVidia driver hangs on VT switch, this never happens. As I wrote above, this bug doesn't occur with Nvidia driver version 535 so the bug has been introduced between version 535 and 545. I cannot debug this further because I don't have the source code. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-545 (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26.1~22.04.1-lowlatency 6.5.13 Uname: Linux 6.5.0-26-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Mar 23 22:08:21 2024 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1904 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nvidia-graphics-drivers-545 UpgradeStatus: Upgraded to jammy on 2023-08-11 (225 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158 ** Affects: nvidia-graphics-drivers-545 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058824 Title: nvidia-driver-545 (and version 550) randomly hangs with compositing manager on VT change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2058824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058162] [NEW] regression: "pacmd dump" reports incorrect status for muted microphone
Public bug reported: pacmd dump | grep mute The "set-source-mute" for my mic should say "no" when my mic is not muted but it always says "yes" nowadays. This used to work earlier. Broken version: $ apt policy pulseaudio-utils pulseaudio-utils: Installed: 1:15.99.1+dfsg1-1ubuntu2.1 Candidate: 1:15.99.1+dfsg1-1ubuntu2.1 I'm pretty sure at least version 1:11.1-1ubuntu7.11 used to work correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio-utils 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.5.0-25.25.1~22.04.1-lowlatency 6.5.13 Uname: Linux 6.5.0-25-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Mar 18 01:38:38 2024 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1898 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2023-08-11 (219 days ago) dmi.bios.date: 10/17/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO 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.:bvr1505:bd10/17/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.init.d.apport: [modified] modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158 mtime.conffile..etc.pulse.daemon.conf: 2021-11-19T14:33:38.709428 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058162 Title: regression: "pacmd dump" reports incorrect status for muted microphone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2058162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972108] [NEW] Git packages should have better title for description
Public bug reported:
Git packages have poor title for the description because GUI tools
assume that the package name is not needed to make the description
understandable.
As a result, when update-manager ("Software Updates") shows list of
updates to install, I get update for "fast, scalable, distributed
revision control system" instead of something related to git.
See the attached screenshot, the only another package in this list with
equally poor description title is the "Virtualization daemon" which is
hard to understand when the package name is not displayed in addition to
the description.
I'd recommend following description titles instead:
git: "Git version control system"
git-cvs: "Git version control system, cvs interoperability"
git-all: "Git version control system, ??? support packages"
I'd also recommend checking the description of "git-all". It definitely doesn't
install all git related packages but only following: git-doc, git-el, git-cvs,
git-mediawiki, git-svn, git-email, git-gui, gitk, gitweb. For example, it
doesn't install git-annex, git-buildpackage-rpm, git-cola, git-repair or
git-review. On the other hand, it installs full emacs installation via
dependencies!
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: git 1:2.17.1-1ubuntu0.11
ProcVersionSignature: Ubuntu 5.4.0-109.123~18.04.1-lowlatency 5.4.178
Uname: Linux 5.4.0-109-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
CurrentDesktop: MATE
Date: Sun May 8 20:41:01 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-01-05 (1219 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: git
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: git (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
** Attachment added: "git-poor-description-title-in-software-updater.png"
https://bugs.launchpad.net/bugs/1972108/+attachment/5587708/+files/git-poor-description-title-in-software-updater.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972108
Title:
Git packages should have better title for description
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git/+bug/1972108/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971895] Re: Warning messages from stat printed on installation with no user crontabs
Confirming this on Ubuntu 18.04.6 LTS while installing updates: Setting up cron (3.0pl1-128.1ubuntu1.1) ... stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory Warning: * is not a regular file! update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults I'm pretty sure I haven't seen this problem with other updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971895 Title: Warning messages from stat printed on installation with no user crontabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1971895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969118] Re: Certificate viewer shows extra bytes for RSA keys
OK, I agree that this is not a security problem but UI issue only. However, note that the UI says "Public key" and before that "Key algorithm: RSA". As such, the public key should not have any extra bytes at the start or at the end, just the public RSA 2048 bit key as is (as desribed by "Key Algorithm" and "Key Size" fields immediately above). Also note that the key displayed by gcr-viewer does not match key value displayed by `openssl x509 -in ... -text`, Google Chrome, nor Firefox. Is this also by design? That said, I agree that gcr-viewer doesn't show the exponent separate from the modulus either so maybe the easiest fix would be to change the label "Public Key" to say "DER Encoded Public Key" to make it obvious that user must decode the encoding of the key by themselves. When I'm viewing PEM encoded key I sure didn't expect to see the public key as DER encoded raw data. A better fix would be to render modulus and exponent as separate fields without any extra bytes. Of course, that would require different code paths for e.g. RSA and x25519. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969118 Title: Certificate viewer shows extra bytes for RSA keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1969118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931871] Re: low 'vfs_cache_pressure' causes bad real world latency
After more experience with different settings it seems that the behavior of vfs_cache_pressure was changed a lot between linux kernel version 5.3 and 5.4. For cases where vfs_cache_pressure=1 did work nicely with version 5.3 you need something in range 30-90 for linux kernel version 5.4 to get the same behavior. I haven't been able to pinpoint which value would be the closest match to old value 1. Also, I haven't seen any information if this is intentional or not, but I guess this could be considered as working okay but requiring different configuration values. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931871 Title: low 'vfs_cache_pressure' causes bad real world latency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1931871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950088] Re: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6, 2)
The NVIDIA GeForce GT 330M device has vendor id 0x10de and device id 0x0a29 and revision 0x00a2. ROM (/firmware) version is listed as "3560". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950088 Title: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6,2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1950088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950088] Re: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6, 2)
According to Apple Mac OS X info this hardware is as follows: MacBook Pro (15-inch, Mid 2010) CPU: 2.53 GHz Intel Core i5 RAM: 4 GB 1067 MHz DDR3 GPU: Intel HD Graphics, 288 MB The hardware *also* has NVIDIA GeForce GT 330M connected (according to OS X self-diagnostics) via 16x PCIe and it has 256 MB of RAM (Mac OS X cannot tell if this is dedicated RAM or part of system RAM like with integrated intel graphics). I believe that the OS X automaticaly switches between these GPUs according to system needs. I would guess that this is also tried by Jammy livecd and it hangs. I guess for this old hardware, automatically turning off the NVIDIA GPU and using just the Intel Graphics could be a good option if the switching is not stable. According to /proc/cpuinfo the Linux kernel successfully run the CPU up to 3.1 GHz so CPU frequency control did work absolutely fine. All the above tests were done with jammy nightly build from date 2021-11-05 obtained here: http://cdimage.ubuntu.com/ubuntukylin/daily- live/current/ and I did write the ISO image to USB memory stick using Ubuntu "Startup Disk Creator" software. I know that some newer MacBooks no longer support booting from USB memory simply by holding down ALT while booting the computer but for this hardware that still appears to work just fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950088 Title: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6,2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1950088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950088] Re: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6, 2)
Here's the full journalctl log for livecd debugging session I reported above. It appears that nautilus was totally hanging because I failed to ever open any file manager windows even after waiting for a long time. Firefox did eventually start and started to work until I tried to open file picker to attach a file to this bug - after that Firefox never recovered either. ** Attachment added: "sudo journalctl --since "2 days ago" after trying to investigate the issue and switching virtual terminals many times" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1950088/+attachment/5538674/+files/2021-11-07-journalctl.full.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950088 Title: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6,2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1950088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950088] [NEW] jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6, 2)
Public bug reported: I tried to use nightly build of Ubuntu 22.04 (jammy) on an old MacBook Pro and if I start with failsafe graphics everything seems to work really well. However, if I boot with default livecd configuration the GPU will hang when I try to launch Firefox. According to journalctl logs it appears that noveau driver or kernel DRM hangs for a long time and the computer appears totally frozen. I can still switch to terminal by pressing Ctrl-Alt-Fn-F3 and waiting a couple of minutes. Waiting for a long time (maybe 10 minutes) the system appears to work correctly again without rebooting the system. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-nouveau 1:1.0.17-1build1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.465 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 13:19:38 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) MachineType: Apple Inc. MacBookPro6,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:skuSystemSKU#:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy reproducible ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950088 Title: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6,2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1950088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921137] Re: mount.ocfs2 causes kernel BUG at lib/string.c:1149!
Another data point here: kernel: [5150033.094216] kernel BUG at lib/string.c:1149! kernel: [5150033.094224] invalid opcode: [#1] SMP NOPTI kernel: [5150033.094229] CPU: 1 PID: 2940890 Comm: mount.ocfs2 Tainted: P OE 5.13.12-051312-generic #202108181219-Ubuntu kernel: [5150033.094233] Hardware name: Gigabyte Technology Co., Ltd. X399 DESIGNARE EX/X399 DESIGNARE EX-CF, BIOS F12i 09/24/2019 kernel: [5150033.094236] RIP: 0010:fortify_panic+0x13/0x15 kernel: [5150033.094244] Code: 35 37 a8 3b 01 48 c7 c7 93 63 01 b6 e8 c9 c9 fe ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 e0 63 01 b6 48 89 e5 e8 b0 c9 fe ff <0f> 0b 48 c7 c7 18 dc c8 b5 e8 df ff ff ff 48 c7 c7 10 dc c8 b5 e8 kernel: [5150033.094248] RSP: 0018:b4f1ee523c50 EFLAGS: 00010246 kernel: [5150033.094252] RAX: 0022 RBX: 9cf5639bb000 RCX: kernel: [5150033.094254] RDX: RSI: 9d033e2589c0 RDI: 9d033e2589c0 kernel: [5150033.094257] RBP: b4f1ee523c50 R08: 9d033e2589c0 R09: b4f1ee523a30 kernel: [5150033.094258] R10: 0001 R11: 0001 R12: 0004 kernel: [5150033.094260] R13: 9cf496853000 R14: 9d00f6a91000 R15: 9cf5639bb291 kernel: [5150033.094262] FS: 7fb7fd6d3b80() GS:9d033e24() knlGS: kernel: [5150033.094265] CS: 0010 DS: ES: CR0: 80050033 kernel: [5150033.094267] CR2: 55f52c08f040 CR3: 00029a09e000 CR4: 003506e0 kernel: [5150033.094270] Call Trace: kernel: [5150033.094276] ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2] kernel: [5150033.094347] ? ocfs2_verify_volume+0x143/0x310 [ocfs2] kernel: [5150033.094410] ocfs2_fill_super+0x262/0xda0 [ocfs2] kernel: [5150033.094473] mount_bdev+0x18d/0x1c0 kernel: [5150033.094478] ? ocfs2_initialize_super.isra.0+0x1070/0x1070 [ocfs2] kernel: [5150033.094539] ocfs2_mount+0x15/0x20 [ocfs2] kernel: [5150033.094599] legacy_get_tree+0x2b/0x50 kernel: [5150033.094604] vfs_get_tree+0x2a/0xc0 kernel: [5150033.094607] ? capable+0x19/0x20 kernel: [5150033.094612] path_mount+0x468/0xa60 kernel: [5150033.094617] do_mount+0x7c/0xa0 kernel: [5150033.094620] __x64_sys_mount+0x8b/0xe0 kernel: [5150033.094623] do_syscall_64+0x61/0xb0 kernel: [5150033.094627] ? syscall_exit_to_user_mode+0x27/0x50 kernel: [5150033.094632] ? __x64_sys_readlink+0x1f/0x30 kernel: [5150033.094635] ? do_syscall_64+0x6e/0xb0 kernel: [5150033.094638] ? irqentry_exit+0x19/0x30 kernel: [5150033.094641] ? exc_page_fault+0x8f/0x170 kernel: [5150033.094645] ? asm_exc_page_fault+0x8/0x30 kernel: [5150033.094649] entry_SYSCALL_64_after_hwframe+0x44/0xae kernel: [5150033.094651] RIP: 0033:0x7fb7fd88cdde kernel: [5150033.094679] Code: 48 8b 0d b5 80 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 82 80 0c 00 f7 d8 64 89 01 48 kernel: [5150033.094682] RSP: 002b:7ffea9610c18 EFLAGS: 0246 ORIG_RAX: 00a5 kernel: [5150033.094686] RAX: ffda RBX: RCX: 7fb7fd88cdde kernel: [5150033.094688] RDX: 55cd6acb10ae RSI: 55cd6c9a7340 RDI: 55cd6c9ac140 kernel: [5150033.094689] RBP: 7ffea9610dc0 R08: 55cd6c9ac0e0 R09: 7ffea960e650 kernel: [5150033.094691] R10: R11: 0246 R12: 7ffea9610cb0 kernel: [5150033.094693] R13: 7ffea9610c30 R14: 55cd6c9ac0e0 R15: kernel: [5150033.094696] Modules linked in: ocfs2_stack_o2cb ocfs2_dlm ocfs2 ocfs2_nodemanager ocfs2_stackglue quota_tree nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_counter nft_limit nft_meta_bridge bridge stp llc snd_seq_dummy vhost_net vhost vhost_iotlb tap rfcomm nf_tables ip6table_filter ip6_tables iptable_filter bpfilter wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 libcurve25519_generic libchacha libblake2s_generic ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink cmac algif_hash openvswitch nsh algif_skcipher nf_conncount af_alg nf_nat bnep nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio crypto_simd snd_hda_codec_hdmi cryptd rapl iwlmvm snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi mac80211 uvcvideo kernel: [5150033.094758] snd_hda_codec videobuf2_vmalloc videobuf2_memops snd_hda_core snd_seq_midi videobuf2_v4l2 btusb snd_seq_midi_event libarc4 btrtl videobuf2_common snd_hwdep snd_rawmidi btbcm btintel videodev snd_seq joydev gigabyte_wmi mc input_leds serio_raw snd_pcm snd_seq_device wmi_bmof bluetooth iwlwifi snd_timer ecdh_generic efi_pstore snd ecc ccp mxm_wmi cfg80211 k10temp soundcore lz4 lz4_compress mac_hid nvidia_uvm(POE) tcp_htcp sch_cake ib_umad
[Bug 1947686] Re: ffmpeg parses AAC+MP4 incorrectly in Ubuntu 20.04 LTS
The file plays correctly both with Firefox and Chrome if you click the link above. ** Summary changed: - ffmpeg parses AAC+MP4 incorrectly in Ubuntu 20.04 LTS + ffmpeg parses AAC+MP4 incorrectly on Ubuntu 20.04 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947686 Title: ffmpeg parses AAC+MP4 incorrectly on Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1947686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947686] Re: ffmpeg parses AAC+MP4 incorrectly in Ubuntu 20.04 LTS
Example file with length of about 8.4 with me speaking numbers 1..10 in Finnish with some background noise. This has been recorded by Apple Safari on iOS 15.0.1 using the MediaRecorder API in HTML5 document. To reproduce the problem, try this: $ time ffmpeg -i iPad-15.0.1-MediaRecorder-audio.mp4 -acodec libmp3lame -ac 2 -qscale:a 9 -ar 48000 -joint_stereo 1 out.mp3 It should result in file called out.mp3 with a length of about 8.4 seconds. With the ffmpeg version in Ubuntu 20.04 LTS the output length is only 1 second. The ffmpeg version distributed with Ubuntu 18.04 LTS and the snap version distributed with Ubuntu 20.04 LTS do work correctly so this bug is strictly about the version distributed via apt on Ubuntu 20.04 LTS. ** Attachment added: "Example audio file (AAC+MP4) recorded by Apple Safari on iOS 15.0.1" https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1947686/+attachment/5534128/+files/iPad-15.0.1-MediaRecorder-audio.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947686 Title: ffmpeg parses AAC+MP4 incorrectly on Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1947686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947686] [NEW] ffmpeg parses AAC+MP4 incorrectly in Ubuntu 20.04 LTS
Public bug reported: The ffmpeg version distributed via apt on Ubuntu 20.04 LTS cannot correctly decode AAC audio in MP4 container when the file is generated by iOS. The ffmpeg version on Ubuntu 18.04 LTS results in correct parsing. Here's working version from Ubuntu 18.04 LTS: $ apt policy ffmpeg ffmpeg: Installed: 7:3.4.8-0ubuntu0.2 Candidate: 7:3.4.8-0ubuntu0.2 Version table: *** 7:3.4.8-0ubuntu0.2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 100 /var/lib/dpkg/status 7:3.4.2-2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages Here's not-working version from Ubuntu 20.04 LTS: $ apt policy ffmpeg ffmpeg: Installed: 7:4.2.4-1ubuntu0.1 Candidate: 7:4.2.4-1ubuntu0.1 Version table: *** 7:4.2.4-1ubuntu0.1 500 500 http://fi.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 500 http://fi.archive.ubuntu.com/ubuntu focal-security/universe amd64 Packages 100 /var/lib/dpkg/status 7:4.2.2-1ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu focal/universe amd64 Packages The ffmpeg version distributed via snap does parse the file correctly but snap version is much slower than the version distributed via apt so I'd much prefer using the apt version if it worked correctly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ffmpeg 7:4.2.4-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Oct 19 11:36:34 2021 InstallationDate: Installed on 2020-12-21 (301 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ffmpeg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ffmpeg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947686 Title: ffmpeg parses AAC+MP4 incorrectly in Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1947686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942935] Re: kernel io hangs during mdcheck/resync
One of the systems was using package linux-generic and in practice Linux pedabackup 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/version_signature Ubuntu 5.4.0-80.90-generic 5.4.124 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1942935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942935] Re: kernel io hangs during mdcheck/resync
I think I've seen this issue once per two different systems so I think this is software issue. Does anybody know if patch in comment #6 is going to be included in Ubuntu 20.04 LTS? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1942935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943048] [NEW] grub-install/dev/sda couldn't be done. A serious error
Public bug reported: I tried to load Ubuntu on a HP laptop, not succesful because "grup- install/dev/sda" failed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 17:51:07 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=fi_FI.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.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.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943048 Title: grub-install/dev/sda couldn't be done. A serious error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1943048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596562] Re: devscripts doesn't depend on equivs (for mk-build-deps)
I agree, if "mk-build-deps" completely fails, it should be Recommends at minimum, probably even Depends. (Tested with Ubuntu 18.04 and I found this bug via Google when trying to figure out why `mk-build-deps` failed.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596562 Title: devscripts doesn't depend on equivs (for mk-build-deps) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1596562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936203] [NEW] nm-applet spams errors continously
Public bug reported: nm-applet emits errors to X session error log continuously. Here's summary from my log (with timestamps removed with perl): $ grep nm-applet .xsession-errors | perl -npe 's/\*\*: \d\d:\d\d:\d\d.\d\d\d: //' | sort | uniq -c 736 (nm-applet:2575): Gtk-CRITICAL gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed 369 (nm-applet:2575): Gtk-WARNING Can't set a parent on widget which has a parent The nm-applet should be fixed to correctly use GTK API. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-77.86~18.04.1-lowlatency 5.4.119 Uname: Linux 5.4.0-77-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: MATE Date: Wed Jul 14 14:21:15 2021 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-01-05 (920 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 84.251.208.1 dev enp3s0 proto dhcp metric 100 84.251.208.0/20 dev enp3s0 proto kernel scope link src 84.251.221.37 metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 IwConfig: enp3s0no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Ethernet (RJ-45) 6e83ecef-cf26-3a9b-9c6b-7a0a538d0ba8 /org/freedesktop/NetworkManager/ActiveConnection/27 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1936203 Title: nm-applet spams errors continously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1936203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591823] Re: "File descriptor \d+ (\S+) leaked on lvs invocation."
I would guess some files are left open when grub_util_pull_lvm_by_command() calls grub_util_exec_pipe() in grub2 /grub-core/osdep/unix/getroot.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/591823 Title: "File descriptor \d+ (\S+) leaked on lvs invocation." To manage notifications about this bug go to: https://bugs.launchpad.net/aptitude/+bug/591823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591823] Re: "File descriptor \d+ (\S+) leaked on lvs invocation."
I got this same warning: $ sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-5.4.0-66-lowlatency linux-headers-5.4.0-73-lowlatency linux-hwe-5.4-headers-5.4.0-66 linux-hwe-5.4-headers-5.4.0-73 linux-image-5.4.0-66-lowlatency linux-image-5.4.0-73-lowlatency linux-modules-5.4.0-66-lowlatency linux-modules-5.4.0-73-lowlatency 0 to upgrade, 0 to newly install, 8 to remove and 0 not to upgrade. After this operation, 714 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 492639 files and directories currently installed.) Removing linux-headers-5.4.0-66-lowlatency (5.4.0-66.74~18.04.2) ... Removing linux-headers-5.4.0-73-lowlatency (5.4.0-73.82~18.04.1) ... Removing linux-hwe-5.4-headers-5.4.0-66 (5.4.0-66.74~18.04.2) ... Removing linux-hwe-5.4-headers-5.4.0-73 (5.4.0-73.82~18.04.1) ... Removing linux-image-5.4.0-66-lowlatency (5.4.0-66.74~18.04.2) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.4.0-66-lowlatency /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.0-77-lowlatency Found initrd image: /boot/initrd.img-5.4.0-77-lowlatency Found linux image: /boot/vmlinuz-5.4.0-74-lowlatency Found initrd image: /boot/initrd.img-5.4.0-74-lowlatency Found linux image: /boot/vmlinuz-5.4.0-73-lowlatency Found initrd image: /boot/initrd.img-5.4.0-73-lowlatency done Removing linux-image-5.4.0-73-lowlatency (5.4.0-73.82~18.04.1) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.4.0-73-lowlatency /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.0-77-lowlatency Found initrd image: /boot/initrd.img-5.4.0-77-lowlatency Found linux image: /boot/vmlinuz-5.4.0-74-lowlatency Found initrd image: /boot/initrd.img-5.4.0-74-lowlatency File descriptor 10 (/var/lib/dpkg/triggers/linux-update-5.4.0-66-lowlatency (deleted)) leaked on lvs invocation. Parent PID 12476: /bin/sh done Removing linux-modules-5.4.0-66-lowlatency (5.4.0-66.74~18.04.2) ... Removing linux-modules-5.4.0-73-lowlatency (5.4.0-73.82~18.04.1) ... $ lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.04.5 LTS Release:18.04 Codename: bionic I would guess this is actually a bug in grub-probe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/591823 Title: "File descriptor \d+ (\S+) leaked on lvs invocation." To manage notifications about this bug go to: https://bugs.launchpad.net/aptitude/+bug/591823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901718] Re: System hangs (freezes) randomly without intel_idle.max_cstate=1
I can confirm that this is somehow related to GPU because when I disabled hardware acceleration in Chrome settings the system has been stable for 100 days. When GPU hardware acceleration is enabled, the system crashes randomly, sometimes within hours, sometimes in a couple of days. I'm pretty sure I never got uptime up to a week when GPU hardware acceleration was enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901718 Title: System hangs (freezes) randomly without intel_idle.max_cstate=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1901718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931976] [NEW] pulseaudio overflow (cause or related to kernel freeze?)
Public bug reported: May be related to old bug https://bugzilla.redhat.com/show_bug.cgi?id=485734 The error appeared when system froze for 30-60 seconds (log timestamps before the freeze were earlier so I don't know the exact moment the system froze, only timestamps for the moment it automatically continue to run again). The only error message found in journalctl was this (hostname is "desktop"): 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large: -377464 bytes (-2139 ms). 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: snd_pcm_dump(): 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: Soft volume PCM 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: Control: PCM Playback Volume 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: min_dB: -51 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: max_dB: 0 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: resolution: 256 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: Its setup is: 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: stream : PLAYBACK 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: access : MMAP_INTERLEAVED 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: format : S16_LE 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: subformat: STD 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: channels : 2 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: rate : 44100 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: exact rate : 44100 (44100/1) 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: msbits : 16 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: buffer_size : 16384 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: period_size : 8192 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: period_time : 185759 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: tstamp_mode : ENABLE 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: tstamp_type : MONOTONIC 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: period_step : 1 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: avail_min: 15802 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: period_event : 0 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: start_threshold : -1 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: stop_threshold : 4611686018427387904 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: silence_threshold: 0 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: silence_size : 0 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: boundary : 4611686018427387904 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: Slave: Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: Its setup is: 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: stream : PLAYBACK 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: access : MMAP_INTERLEAVED 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: format : S16_LE 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: subformat: STD 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: channels : 2 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892 Analog] alsa-util.c: rate : 44100 2021-06-14T15:28:59+0300 desktop pulseaudio[2472]: [alsa-sink-ALC892
[Bug 1931871] [NEW] low 'vfs_cache_pressure' causes bad real world latency
Public bug reported: I have an old workstation running kernel Linux desktop 5.4.0-74-lowlatency #83~18.04.1-Ubuntu SMP PREEMPT Tue May 11 17:19:13 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and when I run echo 1 > /proc/sys/vm/vfs_cache_pressure to allow directory structure to be cached better and then run rsync path/to/A path/to/B multiple times where both A and B contain approximately 6.5 million files (~2.5 TB per directory) I randomly get long pauses (1-15 seconds) which freeze both the desktop and audio output. I get nothing in "sudo journalctl -f" until some software starts to fail (e.g. pulseaudio emits a warning about too high latency). With low "vfs_cache_pressure" the expected behavior would be to be able to keep dentries for those 13 million files and the repeated rsync calls should be pretty fast and not cause high I/O nor memory management load. I've been running with the above setting of "1" for years and I'm pretty sure I haven't noticed this issue before kernel 5.4 series so I think the kernel behavior has degraded. I'm pretty sure I'm not running out of RAM so this is probably a change in the dentry cache behavior or some other part of the kernel memory management. $ free -m totalusedfree shared buff/cache available Mem: 31807964964453262 157126252 Swap: 15901453 136 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-lowlatency-hwe-18.04-edge 5.4.0.74.83~18.04.67 ProcVersionSignature: Ubuntu 5.4.0-74.83~18.04.1-lowlatency 5.4.114 Uname: Linux 5.4.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: MATE Date: Mon Jun 14 15:34:23 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (890 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-meta-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-hwe-5.4 (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/1931871 Title: low 'vfs_cache_pressure' causes bad real world latency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1931871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931871] Re: low 'vfs_cache_pressure' causes bad real world latency
I forgot to add that setting vfs_cache_pressure to e.g. 50 removes the freezing but causes more I/O load because dentries are more often thrown away and need to be re-loaded later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931871 Title: low 'vfs_cache_pressure' causes bad real world latency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1931871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922203] [NEW] docker.io upgrade to 20.10.2-0ubuntu1~20.04.2 failed
Public bug reported:
Updating docker.io from focal-proposed (19.03.8-0ubuntu1.20.04.2 ->
20.10.2-0ubuntu1~20.04.2) fails with this error message:
mv: cannot stat '/var/lib/docker.migrating/*': No such file or directory
dpkg: error processing package docker.io (--configure):
installed docker.io package post-installation script subprocess returned error
exit status 1
After adding "set -x" to "/var/lib/dpkg/info/docker.io.postinst":
# dpkg --configure -a
Setting up docker.io (20.10.2-0ubuntu1~20.04.2) ...
+ . /usr/share/debconf/confmodule
+ [ ! ]
+ PERL_DL_NONLAZY=1
+ export PERL_DL_NONLAZY
+ [ ]
+ exec /usr/share/debconf/frontend /var/lib/dpkg/info/docker.io.postinst
configure 19.03.8-0ubuntu1.20.04.2
+ . /usr/share/debconf/confmodule
+ [ ! 1 ]
+ [ -z ]
+ exec
+ [ ]
+ exec
+ DEBCONF_REDIR=1
+ export DEBCONF_REDIR
+ [ -z 19.03.8-0ubuntu1.20.04.2 ]
+ dpkg --compare-versions 19.03.8-0ubuntu1.20.04.2 le-nl 1.11.2~ds1-1
+ command -v zfs
+ [ -x /usr/sbin/zfs ]
+ modinfo zfs
+ zfs mount
+ awk $2=="/" {print $1}
+ cut -d/ -f1
+ rpool=rpool
+ [ -n rpool ]
+ findmnt -n -o SOURCE /var/lib/docker
+ dockermnt=rpool/var/lib/docker
+ echo rpool/var/lib/docker
+ grep -qE ^$|/ROOT/
+ dpkg --compare-versions 19.03.8-0ubuntu1.20.04.2 le-nl 19.03.8-0ubuntu2
+ mv /var/lib/docker.migrating/* /var/lib/docker/
mv: cannot stat '/var/lib/docker.migrating/*': No such file or directory
dpkg: error processing package docker.io (--configure):
installed docker.io package post-installation script subprocess returned error
exit status 1
Errors were encountered while processing:
docker.io
If it's any help, my /var/lib/docker is zfs, but it's not under rpool/ROOT:
TARGET SOURCE
FSTYPE OPTIONS
/rpool/ROOT/ubuntu_uryi4p
zfs rw,relatime,xattr,posixacl
├─/var/lib rpool/ROOT/ubuntu_uryi4p/var/lib
zfs rw,noatime,xattr,posixacl
│ ├─/var/lib/apt rpool/ROOT/ubuntu_uryi4p/var/lib/apt
zfs rw,noatime,xattr,posixacl
│ ├─/var/lib/docker rpool/var/lib/docker
zfs rw,noatime,xattr,posixacl
** Affects: docker.io (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/1922203
Title:
docker.io upgrade to 20.10.2-0ubuntu1~20.04.2 failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1922203/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914029] [NEW] pulseaudio startup script should not blindly force audible bell
Public bug reported: File /usr/bin/start-pulseaudio-x11 ALWAYS loads module module-x11-bell and uploads audio sample for Pulseaudio if the file /usr/share/sounds/ubuntu/stereo/bell.ogg EXISTS in the filesystem. I have configured only visual bell for everything and therefore any part of the system that forcibly tries to play any kind of audio for bell output is simply broken. At bare minimum, this script should first check if the desktop environment has been configured to use visual bell instead of audible bell before loading the module. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.11 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-lowlatency 5.4.78 Uname: Linux 5.4.0-64-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mira 6634 F pulseaudio /dev/snd/controlC0: mira 6634 F pulseaudio CurrentDesktop: MATE Date: Mon Feb 1 11:48:03 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (757 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO 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.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (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/1914029 Title: pulseaudio startup script should not blindly force audible bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1914029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 285080] Re: incorrect error: there is not enough room on the disk to save
The workaround for this bug is to set environment variable `TMPDIR` pointing to location that has enough space to temporarily hold the downloaded file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/285080 Title: incorrect error: there is not enough room on the disk to save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/285080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898057] Re: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4
After a reboot of the whole fabric (switches and machines), this problem has not resurfaced. Conceivably this could have been a transient error state, so I will close this with "invalid". ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832687] Re: apt-listchanges doesn't work on Ubuntu 19.04
Maybe try changing `which=news` to `which=both` in the configuration file? I'm running 18.04 LTS and I also have following additional line in /etc/apt/listchanges.conf: no_network=false I also use frontend=text but that's just a personal preference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832687 Title: apt-listchanges doesn't work on Ubuntu 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-listchanges/+bug/1832687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903509] Re: libvirt-daemon-system creates system user without marking it as system user for login
Note that according to base-passwd package You *may not* use any uids or gids in the 6-64999 range without *first* requesting an allocation from base-pas...@packages.debian.org and waiting so perhaps libraries that tell if an user account is system or not, need to check if UID is in range from FIRST_SYSTEM_UID to LAST_SYSTEM_UID *or* if it's in range 6-64999. In case the UID is in range 6-64999, a custom lookup should be made to decide if any given UID in this range is a system account or user account. I'm not familiar with the way all those reserved UIDs are used but I'd assume that any UID in that range is special and may require UID specific knowledge about being normal vs system account. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903509 Title: libvirt-daemon-system creates system user without marking it as system user for login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1903509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903509] [NEW] libvirt-daemon-system creates system user without marking it as system user for login
Public bug reported: Package libvirt-daemon-system postinst scripts runs following code: # Allocated UID and GID for libvirt-qemu LIBVIRT_QEMU_UID=64055 LIBVIRT_QEMU_GID=64055 ... groupadd --system --non-unique --gid "$gid" libvirt ... adduser --quiet \ --system \ --ingroup kvm \ --quiet \ --disabled-login \ --disabled-password \ --home /var/lib/libvirt \ --no-create-home \ --gecos "Libvirt Qemu" \ $PARAMETER_UID \ libvirt-qemu However, after this has been done, e.g. lightdm will show "Libvirt Qemu" as a possible user to login. Arguably, the postinst script does the correct thing (it says "--system" and "--disabeld-login") but still package accountsservices picks up this as possible user account to use for login. Perhaps there's some kind of miscommunication between package maintainers about how system accounts are marked as system accounts? At least some packages assume that UID less than 1000 is the only marker for system accounts. According to 'man adduser' the flag '--system' probably does nothing if UID is hardcoded. One possible way to fix this would be to include file /var/lib/AccountsService/users/libvirt-qemu with contents [User] SystemAccount=true to package libvirt-daemon-system. This whole issue is caused by https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=844339 which globally reserves UID above 1000 for system level feature. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libvirt-daemon-system 4.0.0-1ubuntu8.17 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: MATE Date: Mon Nov 9 11:25:56 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (673 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-ip-multicast.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-ip-multicast.xml'] modified.conffile..etc.libvirt.nwfilter.no-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-ip-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-mac-broadcast.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-mac-broadcast.xml'] modified.conffile..etc.libvirt.nwfilter.no-mac-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-mac-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-other-l2-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-other-l2-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-other-rarp-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-other-rarp-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.qemu-announce-self-rarp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/qemu-announce-self-rarp.xml'] modified.conffile..etc.libvirt.nwfilter.qemu-announce-self.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/qemu-announce-self.xml'] modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] modified.conffile..etc.libvirt.qemu.networks.default.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu/networks/default.xml'] ** Affects: libvirt (Ubuntu) Importance: Undecided
[Bug 1903509] Re: libvirt-daemon-system creates system user without marking it as system user for login
The warnings about files in /etc/libvirt/nwfilter/* could also be considered as a bug. Those files are automatically generated and I haven't modified those files. If libvirt is supposed to take care of these files they probably belong under /var/lib/libvirt instead of /etc/libvirt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903509 Title: libvirt-daemon-system creates system user without marking it as system user for login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1903509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903449] [NEW] accountsservice displays "Libvirt Qemu"
Public bug reported: Installing libvirt-manager results in account libvirt-qemu being created. This user has config in /etc/passwd like follows: libvirt-qemu:x:64055:125:Libvirt Qemu,,,:/var/lib/libvirt:/usr/sbin/nologin The "nologin" should be pretty clear signal that this account is not usable for logging in. Despite this, this account is offered in visual login (e.g. lightdm). The computation for possible user accounts is handled by package accountsservice. A workaround is to manually list this user as system user: echo -e "[User]\nSystemAccount=true" > /var/lib/AccountsService/users/libvirt-qemu However, as this user cannot be logged in (/etc/shadow contains "!" as the password hash, too) it never makes any sense to show this in login screen even without the above manual configuration. Related: bug 857651 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: accountsservice 0.6.45-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 8 16:54:24 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (672 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: accountsservice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: accountsservice (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/1903449 Title: accountsservice displays "Libvirt Qemu" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1903449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901718] [NEW] System hangs (freezes) randomly without intel_idle.max_cstate=1
Public bug reported: Maybe related: https://bugzilla.kernel.org/show_bug.cgi?id=109051 This system has CPU Intel i5-3570k (no overclocking) and the system suffers from random hangs (total freeze with no response to power button, SysRq combinations and nothing in any logs). The hang seems to be related to Google Chrome so it might be related to GPU (intel HD 4000) rendering. Adding intel_idle.max_cstate=1 seems to help a lot. Without this kernel flag, the system did hang randomly between 15 min and a couple of days. With this flag the system has frozen first time today after uptime of 3 weeks. So it seems that this CPU is also affected by issues described in the above linked kernel bug. However, as the system did hang earlier today, even this workaround is not perfect. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-lowlatency-hwe-18.04-edge 5.4.0.52.57~18.04.46 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: MATE Date: Tue Oct 27 16:56:35 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (660 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-meta-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-hwe-5.4 (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/1901718 Title: System hangs (freezes) randomly without intel_idle.max_cstate=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1901718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901718] Re: System hangs (freezes) randomly without intel_idle.max_cstate=1
$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz stepping: 9 microcode : 0x21 cpu MHz : 3147.576 cache size : 6144 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds bogomips: 6799.83 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901718 Title: System hangs (freezes) randomly without intel_idle.max_cstate=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1901718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898057] Re: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4
** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898057] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416154/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898057] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416156/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898057] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416155/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898057] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416157/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898057] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416159/+files/WifiSyslog.txt ** Description changed: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] - Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] - Kernel driver in use: mlx4_core + Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] + Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel: [52642.480273] __do_softirq+0xe4/0x2da kernel: [52642.480278] irq_exit+0xae/0xb0 kernel: [52642.480282] smp_apic_timer_interrupt+0x79/0x130
[Bug 1898057] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416158/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898057] Re: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4
apport information ** Package changed: linux-hwe-5.4 (Ubuntu) => linux (Ubuntu) ** Tags added: apport-collected bionic ** Description changed: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel: [52642.480273] __do_softirq+0xe4/0x2da kernel: [52642.480278] irq_exit+0xae/0xb0 kernel: [52642.480282] smp_apic_timer_interrupt+0x79/0x130 kernel: [52642.480285] apic_timer_interrupt+0xf/0x20 kernel: [52642.480286] kernel: [52642.480292] RIP: 0010:cpuidle_enter_state+0xbc/0x440
[Bug 1898057] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416153/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898057] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416152/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898057] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416151/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898057] [NEW] Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4
Public bug reported: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel: [52642.480273] __do_softirq+0xe4/0x2da kernel: [52642.480278] irq_exit+0xae/0xb0 kernel: [52642.480282] smp_apic_timer_interrupt+0x79/0x130 kernel: [52642.480285] apic_timer_interrupt+0xf/0x20 kernel: [52642.480286] kernel: [52642.480292] RIP: 0010:cpuidle_enter_state+0xbc/0x440 kernel: [52642.480294] Code: ff e8 98 f6 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 2b 74 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 kernel:
[Bug 1896251] Re: rsync --delete-missing-args fails with "error: protocol incompatibility"
Minimal test case (run in empty directory): mkdir -p a/1 b/1; echo "/1/2/3" > list; rsync --delete-missing-args --files-from=list a b Example output: file has vanished: ".../rsync-bug/a/1/2" ABORTING due to invalid path from sender: 1/2/3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896251 Title: rsync --delete-missing-args fails with "error: protocol incompatibility" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1896251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896251] Re: rsync --delete-missing-args fails with "error: protocol incompatibility"
I forgot to mention that according to https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=863334 this issue does not exist in version 3.1.1-3. That should help pinpointing the actual problem if you want to backport the fix instead of upgrading the whole rsync package to latest version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896251 Title: rsync --delete-missing-args fails with "error: protocol incompatibility" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1896251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896251] [NEW] rsync --delete-missing-args fails with "error: protocol incompatibility"
Public bug reported: Running rsync --delete-missing-args --files-from=... fails with error message like ABORTING due to invalid path from sender: dir1/dir2/dir3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] if the listed directories are trying to delete full subtree of files. According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has been fixed in version 3.2.2. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334 Could you update the rsync package or backport the fix? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 18 18:27:53 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (621 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Bug watch added: Debian Bug tracker #863334 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896251 Title: rsync --delete-missing-args fails with "error: protocol incompatibility" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1896251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543919] Re: Remove EISA support from main kernel image and make it M (modular)
Still warning messages emitted to kernel log each boot. Ubuntu 20.04.1 LTS 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I'm running over 10 year old systems and I don't need built-in support for EISA. Does anybody even know anybody running old enough hardware to require built-in support? Does anybody even know a use case where a module wouldn't be enough? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543919 Title: Remove EISA support from main kernel image and make it M (modular) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Same issue here with Bose QC35 II and Thinkpad X1 Extreme (2nd gen). Audio profile works just fine, but headset does not play any sound and the microphone does not get any input. It was like this already in April and currently on a fresh install of 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886163] Re: systemd-resolved emits totally useless warning
Maybe related: bug 1785383 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886163 Title: systemd-resolved emits totally useless warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1886163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886163] Re: systemd-resolved emits totally useless warning
Maybe related: bug 1796501 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886163 Title: systemd-resolved emits totally useless warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1886163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886163] [NEW] systemd-resolved emits totally useless warning
Public bug reported: With systemd-resolved taking care of resolving DNS requests, it will emit following warning message when domain fails to resolve: Jul 02 07:19:22 balancer1 systemd-resolved[1269]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. This warning message is missing information about the process that's trying to resolve a domain and (this part is the more important bit) information about the domain that systemd-resolved is trying to resolve in the first place. If the warning message cannot be made meaningful, it should be dropped for good. I'd prefer to log at least the domain name that was being tried to be resolved. Having pid and name of the process that needed the information would be a plus. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jul 3 11:59:22 2020 InstallationDate: Installed on 2019-05-22 (407 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M MachineType: Dell Inc. PowerEdge R230 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=41607337-6732-464c-b97c-429504aa1b23 ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-01 (31 days ago) dmi.bios.date: 12/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0FRVY0 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.asset.tag: lb1.peda.net dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd12/06/2018:svnDellInc.:pnPowerEdgeR230:pvr:rvnDellInc.:rn0FRVY0:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R230 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R230 dmi.sys.vendor: Dell Inc. ** Affects: systemd (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/1886163 Title: systemd-resolved emits totally useless warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1886163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
Could somebody that is seeing this problem try to boot with kernel flag "iommu=off". Some hardware that used to work with older kernels may be broken and fails to work with modern kernels which default to using IOMMU. Note that disabling IOMMU is a heavy handed workaround, not a proper fix. For more information about IOMMU, see https://heiko-sieger.info /iommu-groups-what-you-need-to-consider/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883258] [NEW] Caja file properties does not wrap exif text data
Public bug reported: Steps to reproduce: With Caja folder view active, click a JPEG image with right mouse button and select "Properties" from the context menu. This opens a properties window which will contain tab "Image" if the image contains Exif data. Actual results: In case "Keywords" field (maybe others, I hit this case with a stock photo) contains a very long string without spaces, the whole window will be rendered overly wide often exceeding the monitor width. Expected results: In case "Keywords" field (or any other field) contains a very long string without spaces use horizontal scrollbar for the content instead of forcing the window very wide. As an alternative line wrapping could be forced at the window border. See the attached image; window could only made wider but it couldn't be made narrower. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caja 1.20.2-4ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-lowlatency 5.3.18 Uname: Linux 5.3.0-53-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jun 12 16:20:12 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (523 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: caja UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: caja (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "caja-overly-wide-window-due-exif-keywords.png" https://bugs.launchpad.net/bugs/1883258/+attachment/5383264/+files/caja-overly-wide-window-due-exif-keywords.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883258 Title: Caja file properties does not wrap exif text data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1883258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15
See also: https://www.smartmontools.org/wiki/SAT-with-UAS-Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15
For more information about this issue, see https://askubuntu.com/a/1106020/50254 TL;DR: Linux kernel disables 12 and 16 bit SATA Commands over UAS when used with Seagate HDD enclosures. This usb_storage quirk is "t" instead of "u" which forces the device into USB BOT mode. The only way to make S.M.A.R.T. to work with USB HDD enclosure is to use UAS without limitations - that is, no quirk of any kind. Note that full UAS support has been disabled on all Seagate enclosures by default because Seagate had such a poor track record with multiple products. The quirk "t" is enough to avoid the issue and it will not cause equal performance slowdown as the "u" quirk. Note that if you disable all quirks with known-bad Seagate enclosure the S.M.A.R.T. will work but you risk random data corruption if you write any data on the disk. I guess remounting the disk read-only, disabling the "t" quirk, doing S.M.A.R.T. query, re-enable the "t" quirk and remounting read- write could be considered a safe workaround if you really need the S.M.A.R.T. data. More details about possible usb_storage.quirks: https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877571] [NEW] bash is missing feature to use keyword if identically named alias exists
Public bug reported: If following command is run (sleep 1 & sleep 1 & time wait); date bash is supposed to run two commands in parallel, wait for both to complete and the run third command. However, if current environment has following alias configured alias time='/usr/bin/time -v' then the above command will fail with /usr/bin/time: cannot run wait: No such file or directory and the final command is run without a wait. Bash already has "command" to force interpretation as system command and "builtin" to force interpretation as built-in command. However bash is missing "keyword" to force interpretation as keyword. One should be able to write (sleep 1 & sleep 1 & keyword time wait); date to force time to be interpreted as bash keyword. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bash 4.4.18-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-lowlatency 5.3.18 Uname: Linux 5.3.0-51-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: MATE Date: Fri May 8 15:48:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (488 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (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/1877571 Title: bash is missing feature to use keyword if identically named alias exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1877571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869925] Re: syslog 50GB in a few hours
I have gotten the same kind of errors involving "dcn20_setup_gsl_group_as_lock" function both with in-kernel and AMD's own Pro driver. This happens every time when I run either a game or a video player in fullscreen mode. Additionally any kind of monitor screensaver or power saving mode will sooner or later cause a GPU crash which kills the whole window manager. The amdgpu driver is laughably buggy (in addition to RX 5700 apparently having hardware bugs involving GPU resets which require either silicon fixes or firmware microcode updates). Been waiting for about half a year for working drivers, still waiting... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869925 Title: syslog 50GB in a few hours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1869925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870427] Re: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127
Same issue occurred here during 19.10 -> 20.04 upgrade. Configuration file '/etc/default/smartmontools' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** smartmontools (Y/I/N/O/D/Z) [default=N] ? D sh: 1: pager: not found diff: standard output: Broken pipe Pager worked fine during the upgrade with packages before and after smartmontools. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870427 Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1870427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
It seems to me that fix https://gitlab.freedesktop.org/xorg/xserver/-/commit/cfc5e5040c934 is the correct one. Is it possible to reproduce the crash with that one patch applied even without all the other proposed fixes? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1745345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861380] Re: Internal display backlight not working on a Intel Apollolake based tablet
Hi, since it now appears that Focal will have 5.4 kernel (1), I tested integrating the upstream kernel patches (2) related to this issue in current Focal kernel master and master-next branches (3). Patches applied smoothly to both branches and with both kernels the display backlight works correctly in my test devices (Intel Apollolake based tablets). BR, Mikko Kovanen 1) https://lists.ubuntu.com/archives/kernel-team/2020-February/107227.html 2) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=8cbf89db294166cc13d90a89422605e0c9f8bbc2 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=6f4261fa86dfe08c34ad99eba66368f43e9dd4c3 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=1788fdf14e518e363bae9d18345d93102f4ee5ad 3) https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861380 Title: Internal display backlight not working on a Intel Apollolake based tablet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862508] [NEW] mate-inhibit-applet causes excessive CPU usage
Public bug reported: Please, apply the fix from https://github.com/mate-desktop/mate-power- manager/commit/8e2902337546222db38a00cc16b3d2bc2e0ef852 to mate-power- manager to fix excessive CPU usage after adding "Inhibit Applet" into MATE panel. Due incorrectly implemented icon drawing code in version 1.20 the icon is constantly redrawn which causes 2-6% CPU usage all the time even if the icon visually does nothing. For more information, see: https://github.com/mate-desktop/mate-power-manager/issues/248 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mate-power-manager 1.20.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-lowlatency 5.3.13 Uname: Linux 5.3.0-28-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: MATE Date: Sun Feb 9 12:44:13 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: mate-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mate-power-manager (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/1862508 Title: mate-inhibit-applet causes excessive CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-power-manager/+bug/1862508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862138] Re: "systemctl stop postgresql" fails to stop postgresql
maybe somewhat related to bug 870379 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862138 Title: "systemctl stop postgresql" fails to stop postgresql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1862138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862138] [NEW] "systemctl stop postgresql" fails to stop postgresql
Public bug reported:
Steps to reproduce (drop the "pgbouncer" for below commands if you only
test barebones postgresql):
systemctl start postgresql pgbouncer && \
systemctl stop pgbouncer postgresql && \
ps auxw | grep ^postgre
No output is expected. However, in reality you get up to 6 running
processes because /lib/systemd/system/postgresql.service is incorrectly
implemented and does not follow the documentation:
man -P cat systemctl | grep -A4 no-block
--no-block
Do not synchronously wait for the requested operation to finish. If
this is not specified, the job will be verified, enqueued and
systemctl will wait until the unit's start-up is completed. By
passing this argument, it is only verified and enqueued.
As such, because --no-block was not used, the "systemctl stop" should wait
until the operation
has finished.
The command "systemctl stop postgresql" should be running something
along the lines
systemctl list-units 'postgresql*' | grep ^postgresql@ | awk '{print
$1}' | xargs -r systemctl stop
before returning unless --no-block is given.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: postgresql-common 173ubuntu0.2
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Feb 5 16:46:04 2020
InstallationDate: Installed on 2017-04-25 (1016 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.8)
PackageArchitecture: all
SourcePackage: postgresql-common
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: postgresql-common (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862138
Title:
"systemctl stop postgresql" fails to stop postgresql
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1862138/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861380] [NEW] Internal display backlight not working on a Intel Apollolake based tablet
Public bug reported: Hi, Problem: With current kernels (both Ubuntu kernels and mainline kernels) the display backlight in one of our tablet variants does not work because i915 GFX driver lacks support for I2C transfers from display initialization VBT sequences and the backlight driver is left uninitialized. Ubuntu version: Ubuntu 20.04 daily build (downloaded on 2020-01-20) Device: Aava Mobile Inari10B tablet (Intel Apollolake platform) Existing fixes: Intel has implement a kernel fix for this problem and it is currently on its way to 5.6 kernel (https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/i915/display/intel_dsi_vbt.c?h=next-20200129=8cbf89db294166cc13d90a89422605e0c9f8bbc2). Unfortunately that change is not working correctly as-is, further fix is currently in drm-intel-next-queued (https://cgit.freedesktop.org/drm/drm-intel/commit/?id=de409661c4c90d63cfc64579edbad0a6b10bd50d), which should also end up in 5.6 kernel because it has a fixes tag referring to the initial fix commit. Background information: Our company produces Intel Apollolake based tablets and some of our customers would like to use Ubuntu as the OS. Optimal situation would be that we could recommend Ubuntu 20.04 LTS release to our customers. Since I was unable to find conclusive information regarding which kernel version is going to end up in Ubuntu 20.04 LTS release, I decided to open this bug to resolve if and how the fix for backlight problem could get included in Ubuntu 20.04 LTS release in it's first version. BR, Mikko Kovanen ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1708 F pulseaudio CasperVersion: 1.438 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 30 07:30:24 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) MachineType: OEM ApolloLake ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: W-02.52 dmi.board.asset.tag: NA dmi.board.name: NA dmi.board.vendor: OEM dmi.board.version: NA dmi.chassis.asset.tag: NA dmi.chassis.type: 10 dmi.chassis.vendor: OEM dmi.chassis.version: NA dmi.modalias: dmi:bvnINSYDECorp.:bvrW-02.52:bd12/11/2019:svnOEM:pnApolloLake:pvrNA:rvnOEM:rnNA:rvrNA:cvnOEM:ct10:cvrNA: dmi.product.family: Apollolake dmi.product.name: ApolloLake dmi.product.sku: 0 dmi.product.version: NA dmi.sys.vendor: OEM ** Affects: linux (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/1861380 Title: Internal display backlight not working on a Intel Apollolake based tablet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857472] [NEW] Bluetooth audio stutters horribly when using A2DP
Public bug reported: Bluetooth audio stutters horribly when trying to use A2DP. The HSP profile works okay, but the quality is horrible then. This has been the case for as long as I can remember (at least from Ubuntu 14.04 days or so, probably earlier), with multiple laptops and multiple Bluetooth headset models. Everything works fine with Android, so it's the Bluez/Pulseaudio/Alsa stack, whichever component. At present time using Ubuntu 18.04 LTS with latest upgrades, Bus 002 Device 010: ID 04bf:0309 TDK Corp. Bluetooth USB dongle and a ATH-M50xBT headset but as said, this is hardly specific to these versions and pieces of hardware. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: mjr8306 F...m pulseaudio /dev/snd/controlC1: mjr8306 F pulseaudio /dev/snd/controlC0: mjr8306 F pulseaudio /dev/snd/timer: mjr8306 f pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 24 21:48:29 2019 InstallationDate: Installed on 2017-09-20 (825 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to bionic on 2018-07-04 (538 days ago) dmi.bios.date: 12/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0T21G7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd12/01/2015:svnDellInc.:pnLatitudeE7440:pvr00:rvnDellInc.:rn0T21G7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. ** Affects: 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/1857472 Title: Bluetooth audio stutters horribly when using A2DP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1857472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 861642] Re: upowerd uses 100% cpu till killed
Any updates? The diagnosis in comment #10 seems to make sense. This has been a problem since 2011 and I still see the same issue on Ubuntu 16.04 LTS with latests patches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/861642 Title: upowerd uses 100% cpu till killed To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/861642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684850] Re: man page claims support for an invalid command line argument
Still broken $ apt policy hardlink hardlink: Installed: 0.3.0build1 Candidate: 0.3.0build1 Version table: *** 0.3.0build1 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684850 Title: man page claims support for an invalid command line argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hardlink/+bug/1684850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834290] Re: Incorrect physical size detected for LG 43UD79-B
Additional info: If I run $ xrandr --dpi 104 then xdpyinfo will display correct dimensions. However, xrandr keeps displaying the incorrect physical dimensions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834290 Title: Incorrect physical size detected for LG 43UD79-B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1834290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834290] Re: Incorrect physical size detected for LG 43UD79-B
Possible problem caused by incorrect physical dimensions: The default mouse cursor is huge (e.g. on desktop). However, most applications have normal sized cursor while the cursor hovers above the application. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834290 Title: Incorrect physical size detected for LG 43UD79-B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1834290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835079] [NEW] mate-session does not honor systemd-inhibit
Public bug reported: mate-session ignores any inhibit values set via systemd-inhibit and honors only settings done via mate-session-inhibit. This should be fixed because Ubuntu 18.04 is trying to inhibit things via systemd-inhibit and mate-session may end up suspending the system even if systemd-inhibit is requesting no suspend. Test case: $ systemd-inhibit --why=TEST --what=sleep --mode=block sleep 10m Select "Suspend" from mate menu. Actual result: System suspends (S3 sleep). Expected result: System turns off the screen and delays the suspend for 10 minutes OR a dialog pops up that says that sleep is currently blocked with buttons "Cancel", "Sleep when possible" and "Force sleep now". The "Sleep when possible" option should wait until sleep is no longer inhibited. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mate-session-manager 1.20.0-1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-lowlatency 4.18.20 Uname: Linux 4.18.0-25-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 2 18:52:43 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (177 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: mate-session-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mate-session-manager (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/1835079 Title: mate-session does not honor systemd-inhibit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-session-manager/+bug/1835079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834994] Re: rsync: --xattrs is extremely slow
Note that this bug is NOT a duplicate of https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1524703 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834994 Title: rsync: --xattrs is extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1834994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834994] [NEW] rsync: --xattrs is extremely slow
Public bug reported: Ubuntu 16.04 LTS repositories contain only rsync version 3.1.1: $ apt policy rsync rsync: Installed: 3.1.1-3ubuntu1.2 Candidate: 3.1.1-3ubuntu1.2 Version table: *** 3.1.1-3ubuntu1.2 500 500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 3.1.1-3ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages However, this version has a bug where flag --xattrs causes very very high CPU usage if source contains lots of unique extended attributes. I'm trying to sync 13 TB (roughly 6.5 M files) with extended attributes and this bug seems to make this slower and slower as the time goes by. The system has been copying the stuff for three weeks (!) now. It's getting slower every day but still seems to make progress so I try to run it to completion. First couple of terabytes suggested that this sync operation should have taken around 4 days. The source directory is used by glusterfs which creates checksums as extended attributes and practically every file has different checksum. Please, update rsync package on Ubuntu 16.04 to 3.1.2-2 or later. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799143 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rsync 3.1.1-3ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-51-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 2 09:07:49 2019 InstallationDate: Installed on 2015-02-23 (1589 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: rsync UpgradeStatus: Upgraded to xenial on 2016-06-10 (1116 days ago) ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834994 Title: rsync: --xattrs is extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1834994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810683] Re: Suspend does not work in the login screen
Does anybody care about lightdm bugs? I'm still seeing this issue but I haven't found a way to debug it. Is there some environment variable or some other method that can make all g_debug() messages visible from lightdm? Currently no log seems to contain any of the g_debug() messages in the lightdm source code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810683 Title: Suspend does not work in the login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1810683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834290] [NEW] Incorrect physical size detected for LG 43UD79-B
Public bug reported: I have monitor LG 43UD79-B and xrandr cannot correctly detect the dimensions of the monitor: $ xrandr Screen 0: minimum 8 x 8, current 3840 x 2160, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm 3840x2160 60.00*+ 30.00 2560x1440 59.95 1920x1080 60.0059.94 1600x900 60.00 1280x1024 60.02 1280x800 59.81 1280x720 60.0059.94 1152x864 59.96 1024x768 60.00 800x600 60.32 720x480 59.94 640x480 59.9459.93 DP-3 disconnected (normal left inverted right x axis y axis) According to the LG spec (https://www.lg.com/us/monitors/lg-43UD79-B-4k- uhd-led-monitor) the monitor pixel pitch is 0.2451 x 0.2451 mm so the actual panel size should be 941.184 x 529.416 mm instead of reported "600mm x 340mm". The monitor is connected via Nvidia GTX 1060 (6 GB) in case it makes a difference. Also, this monitor has BGR subpixel structure and it seems that every application will incorrectly default to RGB subpixel structure. I'm not sure if this information is supposed to be available via xrandr. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: x11-xserver-utils 7.7+7 ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-51-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.130 Wed Mar 21 03:37:26 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,mousepoll,move,resize,imgpng,wall,animation,grid,fade,place,vpswitch,gnomecompat,session,workarounds,expo,scale,ezoom] CompositorRunning: None CurrentDesktop: MATE Date: Wed Jun 26 10:06:35 2019 DistUpgraded: 2016-06-10 11:06:21,514 WARNING no activity on terminal for 300 seconds (Applying changes) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-50-lowlatency, x86_64: installed bbswitch, 0.8, 4.15.0-51-lowlatency, x86_64: installed nvidia-384, 384.130, 4.15.0-50-lowlatency, x86_64: installed nvidia-384, 384.130, 4.15.0-51-lowlatency, x86_64: installed GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:865b] InstallationDate: Installed on 2015-02-23 (1583 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-lowlatency root=UUID=254cacdb-f61b-45a6-9885-37afd2b598ce ro libata.noacpi=1 quiet splash vt.handoff=7 SourcePackage: x11-xserver-utils UpgradeStatus: Upgraded to xenial on 2016-06-10 (1110 days ago) dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO 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.:bvr1101:bd02/04/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO: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.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Bug 1834206] [NEW] fc-match -v reports rgba:1 instead of rgba:2 with BGR display
Public bug reported:
I have a BGR display so I really would like to have BGR subpixel
rendering. I'm having major trouble getting fc-match to emit correct
info.
$ fc-match -v | grep -E 'rgba|lcdfilter|antialias|hintstyle|dpi'
antialias: True(w)
hintstyle: 2(i)(w)
dpi: 75(f)(s)
rgba: 1(i)(w)
lcdfilter: 1(i)(w)
$ ls -l /etc/fonts/conf.d/10*
lrwxrwxrwx 1 root root 31 2016-08-16 22:18 /etc/fonts/conf.d/10-antialias.conf
-> ../conf.avail/10-antialias.conf
lrwxrwxrwx 1 root root 30 2019-06-14 12:27 /etc/fonts/conf.d/10-autohint.conf
-> ../conf.avail/10-autohint.conf
lrwxrwxrwx 1 root root 29 2016-08-16 22:18 /etc/fonts/conf.d/10-hinting.conf ->
../conf.avail/10-hinting.conf
lrwxrwxrwx 1 root root 36 2016-08-16 22:18
/etc/fonts/conf.d/10-hinting-slight.conf -> ../conf.avail/10-hinting-slight.conf
lrwxrwxrwx 1 root root 40 2016-08-16 22:18
/etc/fonts/conf.d/10-scale-bitmap-fonts.conf ->
../conf.avail/10-scale-bitmap-fonts.conf
lrwxrwxrwx 1 root root 35 2019-06-13 12:16
/etc/fonts/conf.d/10-sub-pixel-bgr.conf -> ../conf.avail/10-sub-pixel-bgr.conf
$ strace -e trace=file fc-match -v 2>&1 | grep "open.*bgr"
open("/etc/fonts/conf.d/10-sub-pixel-bgr.conf", O_RDONLY|O_CLOEXEC) = 5
$ gsettings list-recursively | grep bgr
com.canonical.unity-greeter xft-rgba 'bgr'
org.cinnamon.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.gnome.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.cinnamon.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.gnome.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.mate.font-rendering rgba-order 'bgr'
Is there some documented reason that fc-match fails to report correct
subpixel order given this config? Is there some another configuration
file that I must modify or create to get fc-match to correctly declare
BGR subpixel structure?
Also, the dpi above is incorrect too, the correct value would be near
96.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-lowlatency 4.15.18
Uname: Linux 4.15.0-51-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Jun 25 16:50:15 2019
InstallationDate: Installed on 2015-02-23 (1583 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: fontconfig
UpgradeStatus: Upgraded to xenial on 2016-06-10 (1110 days ago)
** Affects: fontconfig (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834206
Title:
fc-match -v reports rgba:1 instead of rgba:2 with BGR display
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1834206/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759008] Re: Revert automatic suspend by default for bionic?
Still broken with MATE desktop on Ubuntu 18.04.2 LTS. If I run mate- power-preferences and select ON AC Power - Put computer to sleep when inactive for: [never] the computer still automatically sleeps (enters S3) after 20 minutes. $ grep -C1 sleep-inactive-ac-timeout /usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override [org.gnome.settings-daemon.plugins.power] sleep-inactive-ac-timeout = 0 I've tried to manually run $ systemd-inhibit --mode=block sleep 2h but the system still enters S3 after 20 minutes unless I disable screen saver using mate-inhibit-applet. $ apt policy mate-desktop mate-desktop: Installed: 1.20.1-2ubuntu1 Candidate: 1.20.1-2ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759008 Title: Revert automatic suspend by default for bionic? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1759008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804467] Re: gnome-shell: stray configure notify event
The same bug has also been for at least 2 years present in the Linux Mint Cinnamon, which is based on Gnome. More information: https://bugreports.qt.io/browse/QTBUG-75312 https://bugreports.qt.io/browse/QTBUG-71671 https://github.com/linuxmint/cinnamon/issues/8546 ** Bug watch added: github.com/linuxmint/cinnamon/issues #8546 https://github.com/linuxmint/cinnamon/issues/8546 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804467 Title: gnome-shell: stray configure notify event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1804467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)
This bug is still relevant for Bionic. Any info about possible backport? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691908 Title: fstab binds appear as mounts (x-gvfs-hide is being ignored) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1691908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808133] Re: python3-apport emits a deprecation warning
Could this be fixed for bionic, too? $ python3 -Wall -c '1/0' /usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import fnmatch, glob, traceback, errno, sys, atexit, locale, imp Traceback (most recent call last): File "", line 1, in ZeroDivisionError: division by zero $ lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808133 Title: python3-apport emits a deprecation warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778555] Re: My Webcam does not work with Cheese
Bug confirmed with three computers, each one using Ubuntu 18.04. Webcam works (tested with Camorama) but Cheese can't detect it. >From command line: (cheese:13203): Gtk-WARNING **: 21:16:31.115: Theme parsing error: cheese.css:7:35: The style property GtkScrollbar:min-slider-length is deprecated and shouldn't be used anymore. It will be removed in a future version ** Message: 21:16:31.161: cheese-application.vala:211: Error during camera setup: <> (cheese:13203): cheese-CRITICAL **: 21:16:31.172: cheese_camera_device_get_name: assertion 'CHEESE_IS_CAMERA_DEVICE (device)' failed (cheese:13203): GLib-CRITICAL **: 21:16:31.172: g_variant_new_string: assertion 'string != NULL' failed (cheese:13203): GLib-CRITICAL **: 21:16:31.172: g_variant_ref_sink: assertion 'value != NULL' failed (cheese:13203): GLib-GIO-CRITICAL **: 21:16:31.172: g_settings_schema_key_type_check: assertion 'value != NULL' failed (cheese:13203): GLib-CRITICAL **: 21:16:31.172: g_variant_get_type_string: assertion 'value != NULL' failed (cheese:13203): GLib-GIO-CRITICAL **: 21:16:31.172: g_settings_set_value: key 'camera' in 'org.gnome.Cheese' expects type 's', but a GVariant of type '(null)' was given (cheese:13203): GLib-CRITICAL **: 21:16:31.172: g_variant_unref: assertion 'value != NULL' failed ** (cheese:13203): CRITICAL **: 21:16:31.172: cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device != NULL' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778555 Title: My Webcam does not work with Cheese To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1778555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778555] Re: My Webcam does not work with Cheese
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778555 Title: My Webcam does not work with Cheese To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1778555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
I would like to add that I noticed quite weird connection between this issue and SD card reader in nuc. When the reader was disabled in bios, the issue persists and when it's enabled, the issue does not occur. More info here in the community thread in Intel forum: https://forums.intel.com/s/question/0D50P4D4D6BSAV/really-weird- problem-in-ethernet-adapter-in-nuc8i5beh-help-needed-in-debugging I returned my nuc so this is no more important for me, but clearly there is some bugs in device-bios-driver combo. Propably enabling sd card reader disables some power saving feture and because of tht the bug is not visible? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
I just bought Intel NUC8I5BEH and have also really annoying problems with Ethernet Connection (6) I219-V (device id 15be). Tried to install ubuntu 18.04 LTS version which _should_ be compatible with that NIC but immediately couple of seconds after connectinc network cable (or loading kernel module) ping latency starts increase to couple hundreds or thousand ms. Also some packet loss starts to occur. I verified that compiling intel driver and loading that kernel module fixed this ping problem so most propably there is problem in kernel driver which is included in 18.04. Could someone else confirm this finding and it's relation to kernel module (ubuntu/intel)? I would really appreciate if someone can reproduce this ping issue with ubuntu 18.04 so I can be sure that there is no hardware issue in my Intel NUC. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811447] [NEW] update-initramfs generates wrong RESUME if no swap + zram
Public bug reported: On a system with swap disabled (removed from /etc/fstab) and package zram-config installed update-initramfs -u will emit something like following: I: The initramfs will attempt to resume from /dev/zram1 I: (UUID=1d4b8573-7eee-43c9-a02a-10a65fc17b8a) I: Set the RESUME variable to override this. Obviously, resuming from zram device without actual non-volatile storage is not going to work. update-initramfs should be fixed to ignore /dev/zram* because otherwise the user must e.g. create file /etc /initramfs-tools/conf.d/resume-none with case-sensitive contents RESUME=none to workaround the issue, which may be a bit hard to guess from the above notice only. See also, somewhat related bug: 1781746 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Jan 11 19:10:41 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (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/1811447 Title: update-initramfs generates wrong RESUME if no swap + zram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1811447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734541] Re: encrypted home-directory is not unmounted on logout
Still happens with Ubuntu LTS 18.04. I can provide additional info if needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734541 Title: encrypted home-directory is not unmounted on logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1734541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810683] [NEW] Suspend does not work in the login screen
Public bug reported: After booting the system and login screen is displayed top right gear- icon contains option to Suspend. However, selecting that action has no results at all (no error message, nothing in any file under /var/log or journalctl). I would like to get the suspend action to work similar to older Ubuntu versions (this system used to run Ubuntu 16.04 LTS and I did a fresh install of 18.04.1 LTS). I have removed package gdm3 and installed lightdm instead because I like the lightdm interface better for our use case. Looking at the source code in liblightdm-gobject/power.c suggests that lightdm_get_can_suspend() returns true because I get the suspend option. However, selecting the option does nothing so I would guess that lightdm_suspend() is called but somehow none of the g_debug() log messages never appear anywhere so I cannot debug the problem any further. (The above is just a guess because I didn't have enough time to read the source well enough to figure out if this is the codepath I'm trying to activate.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Sun Jan 6 22:23:20 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (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/1810683 Title: Suspend does not work in the login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1810683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804478] [NEW] netplan dhcp interface with no default route causes causes systemd-networkd-wait-online to hang
Public bug reported: root cause in systemd bug: https://github.com/systemd/systemd/issues/3752 Environment: Ubuntu 18.04 LTS amd64 systemd package version 237-3ubuntu10.9 How to trigger: 1. add netplan interface with dhcpv4 client enabled: enp0s8: addresses: [] dhcp4: true 2. configure dhcp server to NOT give a default route, or any route for that matter 3. reboot 4. systemd-networkd-wait-online will block until dhcp renew is triggered root@sensor1:~# /lib/systemd/systemd-networkd-wait-online --timeout=3 Event loop failed: Connection timed out root@sensor1:~# /lib/systemd/systemd-networkd-wait-online --timeout=3 --ignore=enp0s8 managing: enp0s3 ignoring: lo ignoring: enp0s8 How to fix: Backport upstream changes from systemd (see related systemd ticket). ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: systemd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804478 Title: netplan dhcp interface with no default route causes causes systemd- networkd-wait-online to hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803353] Re: Display freezes (possible i915 freeze/hang)
Extra information: sudo kill -9 via ssh connection did restore the display in working order without restarting the system so I'm pretty sure this is caused by some kind of hang caused by xorg process. Plain kill without -9 did not do anything, though. Perhaps this is caused by some race conditition while xorg is keeping some locks which cause keyboard not to work (e.g. Alt+Ctrl+F1) and the display does not update. After saying that, the system seems to be in some weird state where pretty much all my old X client processess are still running (e.g. Chrome, Opera, Thunderbird) even though the original xorg process does not exists anymore. Thunderbird seems to be eating 100% of a single core. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803353 Title: Display freezes (possible i915 freeze/hang) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1803353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803353] [NEW] Display freezes (possible i915 freeze/hang)
Public bug reported: Xorg suddenly stops updating the display and CTRL+ALT+F1 does not work. The issue happens randomly and does not seem to be related to content being rendered. This time the display hang occurred while I was typing in gnome-terminal. I can successfully ssh into the system from another computer and run ubuntu-bug xorg while the display is frozen. Disconnecting the display port cable and reconnecting does not successfully restore the image. However, after disconnecting the cable and reconnecting, the monitor never resumed from DPMS suspend so the signal emitted did in fact change when I disconnected the cable. The problem occurs both with official lowlatency Ubuntu kernel and custom kernel built from vanilla kernel sources. I haven't found a way to deduce if this is in reality caused by kernel, xorg or the hardware. However, considering that this happens with many different kernel versions, I'd assume this is caused by xorg, instead. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 Uname: Linux 4.18.0-memalloc-watchdog+ x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,mousepoll,move,resize,imgpng,wall,animation,grid,fade,place,vpswitch,gnomecompat,session,workarounds,expo,scale,ezoom] Date: Wed Nov 14 15:23:50 2018 DistUpgraded: 2016-06-10 11:06:21,514 WARNING no activity on terminal for 300 seconds (Applying changes) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] InstallationDate: Installed on 2015-02-23 (1360 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-memalloc-watchdog+ root=UUID=254cacdb-f61b-45a6-9885-37afd2b598ce ro libata.noacpi=1 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-06-10 (887 days ago) dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO 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.:bvr1101:bd02/04/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Sep 6 15:40:48 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41047 vendor DEL xserver.version: 2:1.19.5-0ubuntu2~16.04.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803353 Title: Display freezes (possible i915 freeze/hang) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1803353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622951] Re: bless fails to handle user config
I'm confirming that the patch in #11 fixes the problem. Could this be included in the official package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622951 Title: bless fails to handle user config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bless/+bug/1622951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792585] [NEW] Ubuntu 18.04.1 intall crash
Public bug reported: Ubuntu 18.04.1 (fresh) install crashes after an announcement 'Grub 2 can't be installed to /target'. Tried multiple times, varying disks where the bootloader should be installed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Fri Sep 14 16:45:40 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu ** Description changed: - Ubuntu 18.04 crashes after an announcement 'Grub 2 can't be installed to - /target'. + Ubuntu 18.04.1 (fresh) install crashes after an announcement 'Grub 2 + can't be installed to /target'. Tried multiple times, varying disks where the bootloader should be installed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Fri Sep 14 16:45:40 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Ubuntu 18.04.1 intall crash (Grub 2 target problem) + Ubuntu 18.04.1 intall crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792585 Title: Ubuntu 18.04.1 intall crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1792585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
