[Bug 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
I would like to check to see if the problem is occurring in the kernel and not just in Xorg. Please run: grep . /sys/class/drm/*/modes > modes.txt and then attach the resulting text file here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
Yep, the detailed mode 2560x1440 is in the EDID returned by the monitor: Standard Timings: none Detailed mode: Clock 241.500 MHz, 598 mm x 336 mm 2560 2608 2640 2720 ( 48 32 80) 1440 1443 1448 1481 ( 3 5 33) +hsync -vsync VertFreq: 59.951 Hz, HorFreq: 88.787 kHz Display Product Serial Number: GBLMQS047683 Display Range Limits Monitor ranges (Bare Limits): 24-60 Hz V, 30-140 kHz H, max dotclock 300 MHz Display Product Name: ROG PG278QR -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894942] Autopkgtest regression report (qemu/1:2.11+dfsg-1ubuntu7.33)
All autopkgtests for the newly accepted qemu (1:2.11+dfsg-1ubuntu7.33) for bionic have finished running. The following regressions have been reported in tests triggered by the package: libvirt/4.0.0-1ubuntu8.17 (i386) systemd/237-3ubuntu10.42 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#qemu [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894942 Title: [UBUNTU 20.04] Lost virtio host --> guest notifications cause devices to cease normal operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1894942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901538] Re: Output Device selection messed (Line Out <-> HDMI)
No problem. If there are no more comments after 60 days then the bug will close automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901538 Title: Output Device selection messed (Line Out <-> HDMI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1901538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901724] Re: Systemd user environment generator is not executable.
I thought gnome-shell started its own agent for ssh on startup? Or did you configure your system to run the gnupg agent before starting gnome? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901724 Title: Systemd user environment generator is not executable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1901724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787332] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from systemd_logind_vtenter()
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen ...") from xf86VTEnter() from
systemd_logind_vtenter()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
systemd_logind_vtenter()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787332
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
systemd_logind_vtenter()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1787332/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791981] Re: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
It looks like bug 1897530 might cover this but it's unclear. The fix for that is only in Ubuntu 20.10 so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1791981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
It exists in queue https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=network, which is network manager 1.22.10-1ubuntu2.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900747] Re: enabling ipv6 support broke ipv4 CIDR access list
I upgraded to the version in -proposed and verified that my IPv4 allow config works. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900747 Title: enabling ipv6 support broke ipv4 CIDR access list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conserver/+bug/1900747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901779] Re: Wireless-AC 9560 not working after reboot
** 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/1901779 Title: Wireless-AC 9560 not working after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Autopkgtest regression report (plymouth/0.9.5-0ubuntu2.1)
All autopkgtests for the newly accepted plymouth (0.9.5-0ubuntu2.1) for groovy have finished running. The following regressions have been reported in tests triggered by the package: systemd/246.6-1ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#plymouth [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: Boot animation never finishes, especially when external monitors (or just more than one) are connected To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901074] Re: [SRU] Enable some arm64 optimizations
I don't see these changes in groovy at all, is there a reason why? ** Changed in: ruby2.7 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901074 Title: [SRU] Enable some arm64 optimizations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby2.7/+bug/1901074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901755] Re: "btrfs subvolume list" sporadically segfaults with linux-image-5.4.0-52-generic
I'm currently not running the affected kernel version, since the system is being used as a backup-target (hence the high subvolume count), therefore I cannot provide the requested log. My initial bug report contains the information that should help determining which commit is missing from the kernel. ** 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/1901755 Title: "btrfs subvolume list" sporadically segfaults with linux- image-5.4.0-52-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901782] [NEW] the upgrade from ubuntu 16.04.12 to last one does'nt work
Public bug reported: Setting up tex-common (6.04ubuntu1) ... Ignoring /etc/texmf/texmf.d/05TeXMF.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/15Plain.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/45TeXinputs.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/55Fonts.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/65BibTeX.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/75DviPS.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/80DVIPDFMx.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/85Misc.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/90TeXDoc.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/95NonPath.cnf during generation of texmf.cnf, please remove manually! Warning: Old configuration style found in /etc/texmf/updmap.d Warning: For now these files have been included, Warning: but expect inconsistencies. Warning: These packages should be rebuild with tex-common. Warning: Please see /usr/share/doc/tex-common/NEWS.Debian.gz Warning: found file: /etc/texmf/updmap.d/00updmap.cfg Warning: found file: /etc/texmf/updmap.d/10lmodern.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-base.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-latex-base.cfg Running mktexlsr. This may take some time... done. Running updmap-sys. This may take some time... updmap-sys failed. Output has been stored in /tmp/updmap.pTK5lGmo Please include this file if you report a bug. Sometimes, not accepting conffile updates in /etc/texmf/updmap.d causes updmap-sys to fail. Please check for files with extension .dpkg-dist or .ucf-dist in this directory dpkg: error processing package tex-common (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: tex-common E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.32 ProcVersionSignature: Ubuntu 4.4.0-193.224-generic 4.4.236 Uname: Linux 4.4.0-193-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.25 Architecture: i386 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue Oct 27 18:56:09 2020 InstallationDate: Installed on 2012-06-21 (3050 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to xenial on 2017-03-15 (1322 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug dist-upgrade i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901782 Title: the upgrade from ubuntu 16.04.12 to last one does'nt work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1901782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901784] [NEW] configuration file without pid causes "Bad magic in options.c, line 1059" crash on SIGHUP
Public bug reported: In focal/universe (Ubuntu 20.04.1 LTS), stunnel4 version 3:5.56-1 has a build patch named 04-restore-pidfile-default.patch This patch defines a constant string PIDFILE and uses this constant string in the lines: case CMD_SET_DEFAULTS: new_global_options.pidfile=PIDFILE; (options.c line 1051-1052) after patch. When SIGHUP is received, stunnel reloads this configuration file. During this process, it attempts to free the pidfile path string from the current configuration: case CMD_FREE: tmp=global_options.pidfile; global_options.pidfile=NULL; str_free(tmp); Here, attempting to str_free() the string literal triggers the "Bad magic" error and crashes stunnel. I *believe* the correct fix is to modify patch #04 to read: case CMD_SET_DEFAULTS: new_global_options.pidfile=str_dup(PIDFILE); based on the handling of other arguments elsewhere in this function, but I am not sufficiently versed in C programming to know for sure that this is correct and that it will not introduce other errors (for instance, if the default PIDFILE literal will be re-loaded). Additionally, the stunnel4 manpage does not indicate that `pid` is a required setting, only that leaving it blank prevents a pidfile from being created. This bug was encountered using Amazon Elastic File System's `mount.efs` helper that autogenerates a stunnel configuration, launches stunnel with this configuration, then SIGHUP's that stunnel every hour for certificate changes. Reproduction: min.config == foreground=yes client=yes [test] accept = 127.0.0.1:5001 connect =127.0.0.1:5002 1. Execute `stunnel4 min.config` 2. send a SIGHUP to that stunnel process Expected behavior: configuration reloaded and stunnel execution continues Observed behavior: 2020.10.27 23:16:23 LOG5[ui]: Reading configuration from file /root/min.config 2020.10.27 23:16:23 LOG5[ui]: UTF-8 byte order mark not detected 2020.10.27 23:16:23 LOG5[ui]: FIPS mode disabled 2020.10.27 23:16:23 LOG4[ui]: Service [test] needs authentication to prevent MITM attacks 2020.10.27 23:16:23 LOG5[ui]: Configuration successful INTERNAL ERROR: Bad magic at options.c, line 1059 Aborted (core dumped) ** Affects: stunnel4 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - conifugration file without pid causes "Bad magiic in options.c, line 1059" crash on SIGHUP + configuration file without pid causes "Bad magic in options.c, line 1059" crash on SIGHUP -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901784 Title: configuration file without pid causes "Bad magic in options.c, line 1059" crash on SIGHUP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1901784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858351] Re: Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from AbortServer() from FatalError("no screens found")
*** This bug is a duplicate of bug 1813897 ***
https://bugs.launchpad.net/bugs/1813897
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Summary changed:
- Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("no screens found")
+ Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError() from InitOutput()
** Summary changed:
- Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError() from InitOutput()
+ Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("AddScreen/ScreenInit failed for driver %d\n")
from InitOutput()
** This bug has been marked a duplicate of bug 1813897
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("AddScreen/ScreenInit failed for driver %d\n")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858351
Title:
Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("AddScreen/ScreenInit failed for driver
%d\n") from InitOutput()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1858351/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276804] Re: Xorg crashed with SIGABRT in OsAbort(no screens found?)
Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 14.04 (trusty) reached end-of-life on April 28, 2017
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/UbuntuGNOME#Support
https://lists.ubuntu.com/archives/ubuntu-gnome/2017-March/004211.html
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from
WakeupHandler()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276804
Title:
Xorg crashed with SIGABRT in OsAbort(no screens found?)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1276804/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276804] Re: Xorg crashed with SIGABRT in OsAbort(no screens found?)
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276804 Title: Xorg crashed with SIGABRT in OsAbort(no screens found?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1276804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1545158] Re: Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no screens found")
*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort()
+ Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no screens
found")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545158
Title:
Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no
screens found")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1545158/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543141] Re: Xorg crashed with SIGABRT in OsAbort()
There's not enough information here to tell which FatalError this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543141 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543706] Re: Xorg crashed with SIGABRT in OsAbort()
I can't tell *which* FatalError this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543706 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1545103] Re: Xorg crashed with SIGABRT in raise()
There's not enough information here to tell which FatalError this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545103 Title: Xorg crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1545103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866859] Re: SRU: backport Python 3.6.12, 3.7.9 and 3.8.6 to bionic
There seems to be at least one security issue with the current version of Python 3.8 in Bionic, which is still 3.8.0. See: What’s New In Python 3.8 — Python 3.8.6 documentation https://docs.python.org/release/3.8.6/whatsnew/3.8.html I.e.: Notable changes in Python 3.8.1 Due to significant security concerns, the reuse_address parameter of asyncio.loop.create_datagram_endpoint() is no longer supported. This is because of the behavior of the socket option SO_REUSEADDR in UDP. For more details, see the documentation for loop.create_ So thanks for putting this together, and I hope it is accepted soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866859 Title: SRU: backport Python 3.6.12, 3.7.9 and 3.8.6 to bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/1866859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901778] Re: Thunderbird crashes on start up
thunderbird running fine on my ubuntu 20.10! someone else said not running fine on 20.10 ubuntu mate ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901778 Title: Thunderbird crashes on start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896091] Re: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions
Still broken in 5.8.0-26-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896091 Title: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1896091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893263] Re: Cannot create instance with multiqueue image and vif_type=tap (calico)
debdiff for SRU bionic-stein ** Patch added: "bionic-stein.debdiff" https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1893263/+attachment/5428146/+files/bionic-stein.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893263 Title: Cannot create instance with multiqueue image and vif_type=tap (calico) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893263] Re: Cannot create instance with multiqueue image and vif_type=tap (calico)
debdiff for SRU bionic-train ** Patch added: "bionic-train.debdiff" https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1893263/+attachment/5428145/+files/bionic-train.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893263 Title: Cannot create instance with multiqueue image and vif_type=tap (calico) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893263/+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
Confirmed this continues on Ubuntu 20.10. -- 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 1898784] Re: do-release-upgrade crashed with AttributeError in calcDistUpgrade(): 'DistUpgradeController' object has no attribute 'tasks'
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898784 Title: do-release-upgrade crashed with AttributeError in calcDistUpgrade(): 'DistUpgradeController' object has no attribute 'tasks' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.10-rc1. commit 2628089b74d5a64bd0bcb5d247a18f78d7b6f4d0 Author: Xiao Ni Date: Tue Aug 25 13:42:59 2020 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/2628089b74d5a64bd0bcb5d247a18f78d7b6f4d0 commit 8650a889017cb1f6ea6813ccf83a2e9f6fa49dd3 Author: Xiao Ni Date: Tue Aug 25 13:43:00 2020 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://github.com/torvalds/linux/commit/8650a889017cb1f6ea6813ccf83a2e9f6fa49dd3 commit f046f5d0d79cdb968f219ce249e497fd1accf484 Author: Xiao Ni Date: Tue Aug 25 13:43:01 2020 +0800 Subject: md/raid10: pull codes that wait for blocked dev into one function Link: https://github.com/torvalds/linux/commit/f046f5d0d79cdb968f219ce249e497fd1accf484 commit bcc90d280465ebd51ab8688be86e1f00c62dccf9 Author: Xiao Ni Date: Wed Sep 2 20:00:22 2020 +0800 Subject: md/raid10: improve raid10 discard request Link: https://github.com/torvalds/linux/commit/bcc90d280465ebd51ab8688be86e1f00c62dccf9 commit d3ee2d8415a6256c1c41e1be36e80e640c3e6359 Author: Xiao Ni Date: Wed Sep 2 20:00:23 2020 +0800 Subject: md/raid10: improve discard request for far layout Link: https://github.com/torvalds/linux/commit/d3ee2d8415a6256c1c41e1be36e80e640c3e6359 There is also an additional commit which is required, and was merged after "md/raid10: improve raid10 discard request" was merged. The following commits enable Radid10 to use large discards, instead of splitting into many bios, since the technical hurdles have now been removed. commit e0910c8e4f87bb9f767e61a778b0d9271c4dc512 Author: Mike Snitzer Date: Thu Sep 24 13:14:52 2020 -0400 Subject: dm raid: fix discard limits for raid1 and raid10 Link: https://github.com/torvalds/linux/commit/e0910c8e4f87bb9f767e61a778b0d9271c4dc512 commit f0e90b6c663a7e3b4736cb318c6c7c589f152c28 Author: Mike Snitzer Date: Thu Sep 24 16:40:12 2020 -0400 Subject: dm raid: remove unnecessary discard limits for raid10 Link: https://github.com/torvalds/linux/commit/f0e90b6c663a7e3b4736cb318c6c7c589f152c28 All the commits mentioned follow a similar strategy which was implemented in Raid0 in the below commit, which was merged in 4.12-rc2, which fixed block discard performance issues in Raid0: commit 29efc390b9462582ae95eb9a0b8cd17ab956afc0 Author: Shaohua Li Date: Sun May 7 17:36:24 2017 -0700 Subject: md/md0: optimize raid0 discard handling Link: https://github.com/torvalds/linux/commit/29efc390b9462582ae95eb9a0b8cd17ab956afc0 The commits more or less cherry pick to the 5.8, 5.4 and 4.15 kernels, with the following minor fixups: 1)
[Bug 1898904] Re: Calibre crashes at startup with AttributeError: 'NoneType' object has no attribute 'cancel'
I also applied patch and can confirm it resolves the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898904 Title: Calibre crashes at startup with AttributeError: 'NoneType' object has no attribute 'cancel' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1898904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887359] Re: systemd unit not honors /etc/default/rng-tools
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rng-tools (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/1887359 Title: systemd unit not honors /etc/default/rng-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rng-tools/+bug/1887359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873914] Update Released
The verification of the Stable Release Update for clevis has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873914 Title: initramfs clevis no carrier after 1s, no retry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1873914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896289] Update Released
The verification of the Stable Release Update for clevis has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896289 Title: user should be warned about problems with multiple nics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1896289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896509] Update Released
The verification of the Stable Release Update for clevis has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896509 Title: initramfs always tries to bring up the network even when unnecessary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1896509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896294] Update Released
The verification of the Stable Release Update for clevis has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896294 Title: ip: can't find device '/sys/class/net/enp1s0' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1896294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873593] Update Released
The verification of the Stable Release Update for clevis has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873593 Title: clevis-initramfs no ethernet because of Error: argument " enp2s0" is wrong: "dev" not a valid ifname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1873593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812430] Re: intel hd 500 - j3455 no graphic driver
This bug is closed. Please open a new bug if you have any problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812430 Title: intel hd 500 - j3455 no graphic driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1812430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900009] Re: Window tiled to monitor where most of the window is in instead of where the mouse is.
The fix was written by upstream, and the downstream fix is being packaged by Marco. So I'm not involved in either of those. ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Changed in: mutter (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: mutter (Ubuntu Groovy) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/199 Title: Window tiled to monitor where most of the window is in instead of where the mouse is. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901736] Re: Freeze
This sounds like either bug 1896110 or bug 1874578. Do you think? ** Summary changed: - Xorg freeze + Freeze ** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901736 Title: Freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1901736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877185] Re: maxima-emacs returns LaTeX error
I have resolve the bug, but testing and releasing is necessary.
In a nutshell, the issue is caused by a clash of macro definitions
between `breqn` and `amsmath`.
According to http://mirror.physik-pool.tu-
berlin.de/pub/CTAN/macros/latex/contrib/breqn/breqn.pdf, Sec. 2 (package
loading), a certain order of loading packages in a document's preamble
is necessary:
```
The breqn package automatically loads amsmath to avoid loading order conflicts.
It also automatically loads flexisym and mathstyle, but in some cases these
packages need to be loaded separately.
The canonical order for package loading is:
3\usepackage{amsmath}
\usepackage{flexisym}
\usepackage{breqn}
```
That is, LaTeX template inside `imaxima.el` must be updated; patch is
attached.
A caveat though: there are TWO places where LaTeX template is defined
(see the patch), the bug is fixed by the second; I have introduced the
changes in the first part, but it must be tested.
** Patch added: "latex_breqn_fix.patch"
https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1877185/+attachment/5428184/+files/latex_breqn_fix.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877185
Title:
maxima-emacs returns LaTeX error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1877185/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814983] Re: zfs poor sustained read performance from ssd pool
Hi Colin, thanks so much for giving this another look. I don't see any
references to trying different zfs_arc_meta_limit* settings here!
I raised zfs_arc_meta_limit_percent from the default 75 to 95 and my
system has been running this ripgrep for four hours without falling to
pieces.
I think we can declare success on this one!
Thanks
# grep . /sys/module/zfs/parameters/zfs_arc_{dnode,meta}_limit*
/sys/module/zfs/parameters/zfs_arc_dnode_limit:0
/sys/module/zfs/parameters/zfs_arc_dnode_limit_percent:50
/sys/module/zfs/parameters/zfs_arc_meta_limit:0
/sys/module/zfs/parameters/zfs_arc_meta_limit_percent:95
7.97% [kernel] [k] SHA256TransformBlocks
3.33% [kernel] [k] _raw_spin_lock
2.59% [kernel] [k] arc_evict_state
2.39% [kernel] [k] mutex_lock
2.08% [kernel] [k] osq_lock
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
28555 sarnold 20 0 28.648g 0.023t 2160 S 262.8 18.8 546:39.58 rg
1567 root 20 0 0 0 0 R 71.4 0.0 1200:10 arc_reclaim
2 root 20 0 0 0 0 R 23.7 0.0 238:17.77 kthreadd
1966 root 0 -20 0 0 0 D 11.2 0.0 163:24.49 z_rd_int_2
1967 root 0 -20 0 0 0 S 11.2 0.0 163:25.54 z_rd_int_3
1968 root 0 -20 0 0 0 S 11.2 0.0 163:25.52 z_rd_int_4
# zpool iostat 1
capacity operations bandwidth
poolalloc free read write read write
[...]
-- - - - - - -
fst 2.11T 1.52T 13.8K 0 112M 0
srv 1.84T 6.32T 0 0 0 0
-- - - - - - -
fst 2.11T 1.52T 17.4K 0 146M 0
srv 1.84T 6.32T 0 0 0 0
-- - - - - - -
fst 2.11T 1.52T 17.3K 0 147M 0
srv 1.84T 6.32T 0 0 0 0
-- - - - - - -
# arc_summary
ZFS Subsystem ReportTue Oct 27 19:32:40 2020
ARC Summary: (HEALTHY)
Memory Throttle Count: 0
ARC Misc:
Deleted:688.20m
Mutex Misses: 115.54m
Evict Skips:99.92b
ARC Size: 89.14% 56.07 GiB
Target Size: (Adaptive) 9.30% 5.85GiB
Min Size (Hard Limit): 6.25% 3.93GiB
Max Size (High Water): 16:162.90 GiB
ARC Size Breakdown:
Recently Used Cache Size: 81.96% 24.51 GiB
Frequently Used Cache Size: 18.04% 5.39GiB
ARC Hash Breakdown:
Elements Max: 9.78m
Elements Current: 56.79% 5.55m
Collisions: 201.32m
Chain Max: 8
Chains: 736.70k
ARC Total accesses: 12.23b
Cache Hit Ratio:90.87% 11.12b
Cache Miss Ratio: 9.13% 1.12b
Actual Hit Ratio: 90.27% 11.04b
Data Demand Efficiency: 82.63% 666.79m
Data Prefetch Efficiency: 27.20% 14.18m
CACHE HITS BY CACHE LIST:
Most Recently Used: 30.85% 3.43b
Most Frequently Used: 68.49% 7.61b
Most Recently Used Ghost: 0.13% 13.99m
Most Frequently Used Ghost: 0.61% 67.51m
CACHE HITS BY DATA TYPE:
Demand Data: 4.96% 550.94m
Prefetch Data:0.03% 3.86m
Demand Metadata: 94.20% 10.47b
Prefetch Metadata:0.80% 89.48m
CACHE MISSES BY DATA TYPE:
Demand Data: 10.37% 115.85m
Prefetch Data:0.92% 10.32m
Demand Metadata: 82.55% 921.91m
Prefetch Metadata:6.15% 68.73m
L2 ARC Summary: (HEALTHY)
Low Memory Aborts: 116
Free on Write: 21.13k
R/W Clashes:3
Bad Checksums: 0
IO Errors: 0
L2 ARC Size: (Adaptive) 418.26 GiB
Compressed: 90.78% 379.71 GiB
Header Size:0.08% 360.27 MiB
L2
[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()
OK, clarified somewhat now. This bug is back to being about just "no
screens found".
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no
screens found") from dix_main()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543192
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Marco, What the bluetooth module on your machine? Could you please upload the vendor ID:device ID like #49? thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
** Changed in: gnome-shell (Ubuntu) Status: Expired => Incomplete ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901798] Status changed to Confirmed
This change was made by a bot. ** 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/1901798 Title: Wireless-9560 limit speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897934] Autopkgtest regression report (alsa-lib/1.2.2-2.1ubuntu2.1)
All autopkgtests for the newly accepted alsa-lib (1.2.2-2.1ubuntu2.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#alsa-lib [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [SRU][Intel HDA] The initial sound level is set to zero (muted) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830560] Re: suspend
Please try 20.04... Radeon support is much better in newer release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830560 Title: suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901348] Re: Ayatana indicators battery icon disappears
*** This bug is a duplicate of bug 1766108 *** https://bugs.launchpad.net/bugs/1766108 ** This bug has been marked a duplicate of bug 1766108 Battery indicator crashes when unchecking "Show Percentage in Menu Bar" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901348 Title: Ayatana indicators battery icon disappears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1901348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901348] Re: Ayatana indicators battery icon disappears
*** This bug is a duplicate of bug 1766108 *** https://bugs.launchpad.net/bugs/1766108 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ayatana-indicator-application (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/1901348 Title: Ayatana indicators battery icon disappears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1901348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901694] Re: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series]
[39.611] (II) AIGLX: Screen 0 is not DRI2 capable [39.611] (EE) AIGLX: reverting to software rendering 16.04 is just old and you're not getting any (gfx) updates there anymore at this point -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901694 Title: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1901694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ayatana-indicator-power (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/1766108 Title: Battery indicator crashes when unchecking "Show Percentage in Menu Bar" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868207] Re: Fractional scaling window sizes incorrect after resume from suspend
** Tags added: xrandr-scaling -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868207 Title: Fractional scaling window sizes incorrect after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1868207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901803] [NEW] package grub-efi-amd64-signed 1.142.8+2.04-1ubuntu26.6 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess was killed by signal (
Public bug reported: When I command 'sudo apt upgrade', the progress bar stopped at 91%. A kworker related to grub consumed 100% CPU. (It uses only one CPU. The others were idle.) Dmesg message had error about watchdog and it occurred repeatedly. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub-efi-amd64-signed 1.142.8+2.04-1ubuntu26.6 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 28 11:11:25 2020 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess was killed by signal (종료됨) InstallationDate: Installed on 2020-10-03 (24 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.142.8+2.04-1ubuntu26.6 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess was killed by signal (종료됨) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901803 Title: package grub-efi-amd64-signed 1.142.8+2.04-1ubuntu26.6 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess was killed by signal (종료됨) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1901803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
No they're not really. That's just recovery mode, required to log this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246981] Re: Bluetooth devices fail to re-connect after sleep.
That means the bluetooth controller really wakes up after started a scanning. Recent BT 4.0 controllers from Intel or Qualcomm shouldn't have this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246981 Title: Bluetooth devices fail to re-connect after sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901798] [NEW] Wireless-9560 limit speed
Public bug reported: I am having wifi throughput issues. all other devices that connected to my wireless are getting 150 - 200+ Mbps download speed. I have an HP OMEN gaming laptop that cannot get pass 80mbps to download speed. Can you help me out with how to report this? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: krillavilla 5043 F pulseaudio /dev/snd/controlC1: krillavilla 5043 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 21:48:20 2020 InstallationDate: Installed on 2020-06-23 (126 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=98265a4d-5439-415e-b43c-904265a8559a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-19 (9 days ago) dmi.bios.date: 04/24/2019 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8466 dmi.board.vendor: HP dmi.board.version: 68.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 68.21 dmi.modalias: dmi:bvnAMI:bvrF.09:bd04/24/2019:br15.9:efr68.21:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn8466:rvr68.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop dmi.product.sku: 4CC49UA#ABA dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-06-26T00:47:21.524860 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901798 Title: Wireless-9560 limit speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870886] Re: Window scales to 200% after screen unlocked, on desktop with external monitor
Please run this command to send us more information about the machine: apport-collect 1870886 ** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870886 Title: Window scales to 200% after screen unlocked, on desktop with external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870886] Re: Window scales to 200% after screen unlocked
Still reproducible on Groovy. It's not a laptop, it's a desktop with single monitor. Both AMD and Intel GFX have this issue. ** This bug is no longer a duplicate of bug 1868207 Fractional scaling window sizes incorrect after resume from suspend ** Summary changed: - Window scales to 200% after screen unlocked + Window scales to 200% after screen unlocked, on desktop with external monitor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870886 Title: Window scales to 200% after screen unlocked, on desktop with external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
you're using 'nomodeset' boot option which disables things, don't do that -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901797] [NEW] The upgrade to 20.10 is not taking place
Public bug reported: The upgrade fails at new software channel's stage. It states that ubuntu-minimal cannot be located. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.8 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 28 10:11:50 2020 InstallationDate: Installed on 2019-11-13 (349 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2020-10-28 (0 days ago) VarLogDistupgradeAptlog: Log time: 2020-10-28 10:10:59.067532 Log time: 2020-10-28 10:11:17.048911 Log time: 2020-10-28 10:11:39.512525 Log time: 2020-10-28 10:12:01.084165 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901797 Title: The upgrade to 20.10 is not taking place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1901797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890438] Re: Ubuntu Groovy proposed:networkd-dispatcher.service ModuleNotFoundError: No module named 'glib'
[Expired for networkd-dispatcher (Ubuntu) because there has been no activity for 60 days.] ** Changed in: networkd-dispatcher (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890438 Title: Ubuntu Groovy proposed:networkd-dispatcher.service ModuleNotFoundError: No module named 'glib' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1890438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893456] Re: Universal Access - Screen Keyboard Not working
[Expired for ubuntu-docs (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-docs (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893456 Title: Universal Access - Screen Keyboard Not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1893456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893497] Re: error in repositories, reinstalled ubuntu and error on installation, says disk error but is new, I changed recently
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893497 Title: error in repositories, reinstalled ubuntu and error on installation, says disk error but is new, I changed recently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899802] Re: [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander
Sreekanth, what's the target upstream kernel version for this feature? Just want to get a feel for the timing. As you've already submitted these upstream, getting them into 21.04 should be no problem at all. Also, do you expect (or desire) us to pull these back into 5.4 at some point, or are you fine with them landing in the current mainline kernel and find their way into Ubuntu 20.04 via the HWE kernel later next year? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899802 Title: [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427970/+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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] Re: Sound Blaster Audigy 5/Rx cannot be configured as input/output
apport information ** Tags added: apport-collected third-party-packages ulyana ** Description changed: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.10 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ale1149 F pulseaudio + /dev/snd/controlC1: ale1149 F pulseaudio + /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 20 + InstallationDate: Installed on 2020-08-29 (59 days ago) + InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 + IwConfig: + enp3s0no wireless extensions. + + lono wireless extensions. + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + NonfreeKernelModules: nvidia_modeset nvidia + Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] + PackageArchitecture: amd64 + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash + ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-52-generic N/A + linux-backports-modules-5.4.0-52-generic N/A + linux-firmware1.187.3 + RfKill: + + Tags: ulyana third-party-packages + Uname: Linux 5.4.0-52-generic x86_64 + UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/06/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P2.80 + dmi.board.name: Z97 Extreme6 + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. + modified.conffile..etc.pulse.default.pa: [modified] + mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427966/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427971/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427975/+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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901738] [NEW] Installing 20.10 on a multi partion system
Public bug reported: Have 4 disks with 10(?) partitions. Installed on sdc1 as a full disk. Start up to be placed on sda. When finishing, the Grub reports it can't install start up at sda. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-fbc1-450_450.80.02-0ubuntu1_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 18:20:50 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=nb_NO.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nb_NO.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901738 Title: Installing 20.10 on a multi partion system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427976/+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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427973/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427967/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427969/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427972/+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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894896] Re: [linux-azure][hibernation] Mellanox CX4 NIC's TX/RX packets stop increasing after hibernation/resume
SRU submission: https://lists.ubuntu.com/archives/kernel- team/2020-October/114296.html ** Description changed: + [Impact] + Description of problem: In a VM with CX4 VF NIC on Azure, after hibernation/resume, the TX/RX packet counters stop increaseing. This issue doesn't exist in VM with a CX3 VF NIC. This happens to the latest stable release of the linux-azure 5.4.0-1023.23 kernel and the latest mainline linux kernel. + + [Test Case] How reproducible: 100% Steps to Reproduce: 1. Start a VM in Azure that supports Accelerated Networking, and enable hibernation properly (please refer to https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/comments/14 ). Please make sure the VF NIC is CX-4 since the issue doesn't happen to CX-3. 2. Do hibernation from serial console # systemctl hibernate 3. After the VM resumes back, check the MSI interrupt counters in /proc/interrupts for the CX-4 NIC, and also check “ifconfig” (e.g. “ifconfig enP2642s2”) for the RX/TX counters. These counters stop increasing while they should. + [Regression Potential] + + The change touches netvsc and has potential to affect any instances + using accelerated networking. However the fix is straightforward and + it's a clean cherry-pick from 5.9. + + [Other Info] BUG FIX: - The fix is in the net.git tree now: + The fix is in the net.git tree now: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=19162fd4063a3211843b997a454b505edb81d5ce ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894896 Title: [linux-azure][hibernation] Mellanox CX4 NIC's TX/RX packets stop increasing after hibernation/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1894896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894896] Re: [linux-azure][hibernation] Mellanox CX4 NIC's TX/RX packets stop increasing after hibernation/resume
groovy:linux-azure already has the fix that was included by the upstream stable update LP:#1897550. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894896 Title: [linux-azure][hibernation] Mellanox CX4 NIC's TX/RX packets stop increasing after hibernation/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1894896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: Boot animation never finishes, especially when external monitors (or just more than one) are connected
Brian, thanks for the heads up and the links to the docs on how to test... I'll look into this later today then and post back. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: Boot animation never finishes, especially when external monitors (or just more than one) are connected To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] Re: Sound Blaster Audigy 5/Rx cannot be configured as input/output
@Daniel van Vugt: thanks for checking my bug request. I apologise for the missing information: I've just executed the apport-collect and I wish all the necessary information to be attached. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login
Daniel, this seems consistent: so long as I don't load the Dropbox app, I haven't seen the suspend. I don't know if this is the cause but regardless the Dropbox app may help in reproducing this issue? Thanks... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897185 Title: Laptop docked with lid closed, goes to sleep immediately on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427968/+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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427974/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427982/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427977/+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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900777] Re: [amdgpu] Screen freeze
Today's freeze, before uninstalling the driver ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+bug/1900777/+attachment/5427983/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900777 Title: [amdgpu] Screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1900777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427979/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427978/+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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427981/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427980/+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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900747] Re: enabling ipv6 support broke ipv4 CIDR access list
Hello dann, or anyone else affected, Accepted conserver into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/conserver/8.2.4-2ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: conserver (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900747 Title: enabling ipv6 support broke ipv4 CIDR access list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conserver/+bug/1900747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901740] Re: package grub-pc 2.04-1ubuntu26.4 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901740 Title: package grub-pc 2.04-1ubuntu26.4 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1901740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Same story here on Ubuntu 20.10. Kernel version 5.8.0-25-generic on Dell XPS 15 9570, with Intel UHD Graphics 630 (Mobile). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901740] [NEW] package grub-pc 2.04-1ubuntu26.4 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1
Public bug reported: This is the result of responding to a screen prompt while working, something like "System error detected. Send report?" ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub-pc 2.04-1ubuntu26.4 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 27 13:31:47 2020 DuplicateSignature: package:grub-pc:2.04-1ubuntu26.4 Setting up grub-pc (2.04-1ubuntu26.4) ... dpkg: error processing package grub-pc (--configure): installed grub-pc package post-installation script subprocess returned error exit status 1 ErrorMessage: installed grub-pc package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-04-27 (1644 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=UUID=9833c3f1-2502-4486-9b30-622e6e99abb8 ro nouveau.modeset=0 ast.modeset=0 net.ifnames=0 nvidia_drm.modeset=1 vga=normal video=vga16:off Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: grub2 Title: package grub-pc 2.04-1ubuntu26.4 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-06 (20 days ago) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901740 Title: package grub-pc 2.04-1ubuntu26.4 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1901740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901606] Re: security update broke module import in libpam-python, "from httplib2 import Http" fails now
** Also affects: pam-python (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901606 Title: security update broke module import in libpam-python, "from httplib2 import Http" fails now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam-python/+bug/1901606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901741] [NEW] debconf-updatepo fails to setup translations due to crash.c, livepatch.c and livepatch-tray.c
Public bug reported: Steps to reproduce on Focal system: $ git clone -b master https://git.launchpad.net/update-notifier Cloning into 'update-notifier'... ... $ debconf-updatepo ERROR: xgettext failed to generate PO template file because there is non-ASCII string marked for translation. Please make sure that all strings marked for translation are in uniform encoding (say UTF-8), then *prepend* the following line to POTFILES.in and rerun intltool-update: [encoding: UTF-8] debconf-updatepo succeeds when applying the following diff: diff --git a/po/POTFILES.in b/po/POTFILES.in index de4ee8a..f5dd85f 100644 --- a/po/POTFILES.in +++ b/po/POTFILES.in @@ -7,11 +7,8 @@ data/apt_check.py data/apt-cdrom-check data/cddistupgrader -src/crash.c src/cdroms.c src/hooks.c -src/livepatch.c -src/livepatch-tray.c src/update.c src/update-notifier.c [type: gettext/glade]ui/hooks-dialog.ui csmith@uptown:/tmp/update-notifier$ debconf-updatepo csmith@uptown:/tmp/update-notifier$ echo $? 0 ** Affects: update-notifier (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/1901741 Title: debconf-updatepo fails to setup translations due to crash.c, livepatch.c and livepatch-tray.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1901741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901538] Re: Output Device selection messed (Line Out <-> HDMI)
OK, so deletion of pulse config helped. First deletion only temporarly and the weird behavior came back after some switching. But after the second one it seems to be permanently fixed and I can't reproduce the faulty behavior. So I assume it can be seen as fixed?! If it happens again and is reproducible, I'll report again. Thank you for your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901538 Title: Output Device selection messed (Line Out <-> HDMI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1901538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I've updated the description with the SRU bug template. I think this includes all the relevant info? ** Description changed: - I'm trying to run chromium installed via snap in Ubuntu 20.10 when - running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: + [Impact] - > chromium + * Users who select the Wayland session on Ubuntu 20.10 cannot run snap +confined X11 applications, due to gnome-shell no longer listening on an +abstract socket for connections. + + * The fix, which has been accepted into upstream's gnome-3-38 branch +reverts the change removing the abstract socket, and fixes the bug that +prompted it's removal. + + [Test Case] + + * Start with a stock Ubuntu 20.10 desktop install. + + * At the GDM login screen, after selecting your user account use the gear +icon to select the "Ubuntu on Wayland" session, and log in. + + * Ensure Chromium is installed by running "sudo snap install chromium". + + * Try to run "chromium" from the terminal. Without the fix, it will fail +with the error "Unable to open X display". With the fix applied, it +will launch as normal. + + [Regression Potential] + + * The patch modifies the logic gnome-shell uses to launch Xwayland. So +there is a potential that the change could break X11 application +support on the Wayland session. + + * The default configuration for gnome-shell is to launch Xwayland on +session start, so it should be immediately obvious if there are +problems. + + * In addition to checking snapped X11 apps like Chromium, verify that a +few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). + + [Other Info] + + * Running "ss -xlp | grep Xwayland" should show that it is listening on +both "/tmp/.X11-unix/X0" (the regular unix domain socket) and +"@/tmp/.X11-unix/X0" (the abstract socket). + + --- + I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: + + > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: [Impact] - * Users who select the Wayland session on Ubuntu 20.10 cannot run snap -confined X11 applications, due to gnome-shell no longer listening on an -abstract socket for connections. + * Users who select the Wayland session on Ubuntu 20.10 cannot run snap + confined X11 applications, due to gnome-shell no longer listening on an + abstract socket for connections. - * The fix, which has been accepted into upstream's gnome-3-38 branch -reverts the change removing the abstract socket, and fixes the bug that -prompted it's removal. + * The fix, which has been accepted into upstream's gnome-3-38 branch + reverts the change removing the abstract socket, and fixes the bug that + prompted it's removal: + +https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] - * Start with a stock Ubuntu 20.10 desktop install. + * Start with a stock Ubuntu 20.10 desktop install. - * At the GDM login screen, after selecting your user account use the gear -icon to select the "Ubuntu on Wayland" session, and log in. + * At the GDM login screen, after selecting your user account use the gear + icon to select the "Ubuntu on Wayland" session, and log in. - * Ensure Chromium is installed by running "sudo snap install chromium". + * Ensure Chromium is installed by running "sudo snap install chromium". - * Try to run "chromium" from the terminal. Without the fix, it will fail -with the error "Unable to open X display". With the fix applied, it -will launch as normal. + * Try to run "chromium" from the terminal. Without the fix, it will fail + with the error "Unable to open X display". With the fix applied, it + will launch as normal. [Regression Potential] - * The patch modifies the logic gnome-shell uses to launch Xwayland. So -there is a potential that the change could break X11 application -support on the Wayland session. + * The patch modifies the logic gnome-shell uses to launch Xwayland. So + there is a potential that the change could break X11
[Bug 1901587] Re: Ctrl+Alt+Shift+R doesn't record screen anymore
*** This bug is a duplicate of bug 1901391 *** https://bugs.launchpad.net/bugs/1901391 ** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901587 Title: Ctrl+Alt+Shift+R doesn't record screen anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1901587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
