[Bug 1809682] Re: "systemctl enable corosync-qdevice.service" fails
Hello Bert,
We are not yet fully disabling sysv related scripts because there are
systems that are not, yet, using systemd. Not for this case, but, one of
these examples is windows WSL environment, where systemd is not
supported yet. Just wanted to mention this to show there are some other
things to be taken in consideration when dropping support, entirely, for
sysv scripts, for example.
Just a quick example on corosync running inside WSL environment:
rafaeldtinoco@lenovo:~$ uname -a
Linux lenovo 4.4.0-18362-Microsoft #476-Microsoft Fri Nov 01 16:53:00 PST 2019
x86_64 x86_64 x86_64 GNU/Linux
rafaeldtinoco@lenovo:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 19.10
Release:19.10
Codename: eoan
$ sudo corosync -f
Mar 20 01:49:47 notice [MAIN ] Corosync Cluster Engine 3.0.1 starting up
Mar 20 01:49:47 info[MAIN ] Corosync built-in features: dbus monitoring
watchdog augeas systemd xmlconf snmp pie relro bindnow
Mar 20 01:49:47 warning [MAIN ] Could not lock memory of service to avoid page
faults: Function not implemented (38)
Mar 20 01:49:47 notice [TOTEM ] Initializing transport (UDP/IP Unicast).
Mar 20 01:49:47 warning [TOTEM ] Could not set traffic priority: Protocol not
available (92)
Mar 20 01:49:47 notice [TOTEM ] The network interface [127.0.0.1] is now up.
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync configuration
map access [0]
Mar 20 01:49:47 info[QB] server name: cmap
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync configuration
service [1]
Mar 20 01:49:47 info[QB] server name: cfg
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync cluster closed
process group service v1.01 [2]
Mar 20 01:49:47 info[QB] server name: cpg
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync profile
loading service [4]
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync resource
monitoring service [6]
Mar 20 01:49:47 warning [WD] Watchdog not enabled by configuration
Mar 20 01:49:47 warning [WD] resource load_15min missing a recovery key.
Mar 20 01:49:47 warning [WD] resource memory_used missing a recovery key.
Mar 20 01:49:47 info[WD] no resources configured.
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync watchdog
service [7]
Mar 20 01:49:47 notice [QUORUM] Using quorum provider corosync_votequorum
Mar 20 01:49:47 notice [QUORUM] This node is within the primary component and
will provide service.
Mar 20 01:49:47 notice [QUORUM] Members[0]:
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync vote quorum
service v1.0 [5]
Mar 20 01:49:47 info[QB] server name: votequorum
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync cluster quorum
service v0.1 [3]
Mar 20 01:49:47 info[QB] server name: quorum
Mar 20 01:49:47 notice [TOTEM ] adding new UDPU member {127.0.0.1}
Mar 20 01:49:47 notice [TOTEM ] A new membership (1:28) was formed. Members
joined: 1
Mar 20 01:49:47 warning [CPG ] downlist left_list: 0 received
Mar 20 01:49:47 notice [QUORUM] Members[1]: 1
Mar 20 01:49:47 notice [MAIN ] Completed service synchronization, ready to
provide service.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809682
Title:
"systemctl enable corosync-qdevice.service" fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync-qdevice/+bug/1809682/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809682] Re: "systemctl enable corosync-qdevice.service" fails
I'm closing up corosync / corosync-* bugs for Focal and will check sysv script tomorrow. For now, I can say that: (c)rafaeldtinoco@clusterdev:~$ sudo systemctl status corosync-qdevice ● corosync-qdevice.service - Corosync Qdevice daemon Loaded: loaded (/lib/systemd/system/corosync-qdevice.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: man:corosync-qdevice systemd is not defaulting to sysv generator anymore when systemd units are available, as you can see above, package corosync-qdevice installed defaults to systemd unit so having both simultaneously won't be a problem to new users (apart from having a tiny extra file at /etc/init.d/ directory). -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1809682 Title: "systemctl enable corosync-qdevice.service" fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync-qdevice/+bug/1809682/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1809682] Re: "systemctl enable corosync-qdevice.service" fails
I'm closing up corosync / corosync-* bugs for Focal and will check sysv script tomorrow. For now, I can say that: (c)rafaeldtinoco@clusterdev:~$ sudo systemctl status corosync-qdevice ● corosync-qdevice.service - Corosync Qdevice daemon Loaded: loaded (/lib/systemd/system/corosync-qdevice.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: man:corosync-qdevice systemd is not defaulting to sysv generator anymore when systemd units are available, as you can see above, package corosync-qdevice installed defaults to systemd unit so having both simultaneously won't be a problem to new users (apart from having a tiny extra file at /etc/init.d/ directory). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809682 Title: "systemctl enable corosync-qdevice.service" fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync-qdevice/+bug/1809682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809682] Re: "systemctl enable corosync-qdevice.service" fails
Hello Bert,
We are not yet fully disabling sysv related scripts because there are
systems that are not, yet, using systemd. Not for this case, but, one of
these examples is windows WSL environment, where systemd is not
supported yet. Just wanted to mention this to show there are some other
things to be taken in consideration when dropping support, entirely, for
sysv scripts, for example.
Just a quick example on corosync running inside WSL environment:
rafaeldtinoco@lenovo:~$ uname -a
Linux lenovo 4.4.0-18362-Microsoft #476-Microsoft Fri Nov 01 16:53:00 PST 2019
x86_64 x86_64 x86_64 GNU/Linux
rafaeldtinoco@lenovo:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 19.10
Release:19.10
Codename: eoan
$ sudo corosync -f
Mar 20 01:49:47 notice [MAIN ] Corosync Cluster Engine 3.0.1 starting up
Mar 20 01:49:47 info[MAIN ] Corosync built-in features: dbus monitoring
watchdog augeas systemd xmlconf snmp pie relro bindnow
Mar 20 01:49:47 warning [MAIN ] Could not lock memory of service to avoid page
faults: Function not implemented (38)
Mar 20 01:49:47 notice [TOTEM ] Initializing transport (UDP/IP Unicast).
Mar 20 01:49:47 warning [TOTEM ] Could not set traffic priority: Protocol not
available (92)
Mar 20 01:49:47 notice [TOTEM ] The network interface [127.0.0.1] is now up.
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync configuration
map access [0]
Mar 20 01:49:47 info[QB] server name: cmap
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync configuration
service [1]
Mar 20 01:49:47 info[QB] server name: cfg
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync cluster closed
process group service v1.01 [2]
Mar 20 01:49:47 info[QB] server name: cpg
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync profile
loading service [4]
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync resource
monitoring service [6]
Mar 20 01:49:47 warning [WD] Watchdog not enabled by configuration
Mar 20 01:49:47 warning [WD] resource load_15min missing a recovery key.
Mar 20 01:49:47 warning [WD] resource memory_used missing a recovery key.
Mar 20 01:49:47 info[WD] no resources configured.
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync watchdog
service [7]
Mar 20 01:49:47 notice [QUORUM] Using quorum provider corosync_votequorum
Mar 20 01:49:47 notice [QUORUM] This node is within the primary component and
will provide service.
Mar 20 01:49:47 notice [QUORUM] Members[0]:
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync vote quorum
service v1.0 [5]
Mar 20 01:49:47 info[QB] server name: votequorum
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync cluster quorum
service v0.1 [3]
Mar 20 01:49:47 info[QB] server name: quorum
Mar 20 01:49:47 notice [TOTEM ] adding new UDPU member {127.0.0.1}
Mar 20 01:49:47 notice [TOTEM ] A new membership (1:28) was formed. Members
joined: 1
Mar 20 01:49:47 warning [CPG ] downlist left_list: 0 received
Mar 20 01:49:47 notice [QUORUM] Members[1]: 1
Mar 20 01:49:47 notice [MAIN ] Completed service synchronization, ready to
provide service.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1809682
Title:
"systemctl enable corosync-qdevice.service" fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync-qdevice/+bug/1809682/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1850238] Re: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels
https://lore.kernel.org/lkml/20200311165806.12365-1-kai.heng.f...@canonical.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850238 Title: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Stéphane, please subscribe to bug 1866368 for your issue. Based on the information in comment #8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744544] Re: I don't know
Please describe the kind of problem you are, or were, experiencing. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1744544 Title: I don't know To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1744544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868189] Re: Low memory situations result in root partition being remounted read-only
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1868189/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868189 Title: Low memory situations result in root partition being remounted read- only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1868189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1340172] Re: [OSCI] Add mamange/unmanage blocks to corosync init scripts
Thank you for taking the time to report this bug. In an effort to keep an up-to-date and valid list of bugs to work on, I have reviewed this report to verify it still requires effort and occurs on an Ubuntu release in standard support, and it does not. Unfortunately this bug is old for us to consider having an sysv-compatible option to put the cluster into maintenance mode. Corosync is also being managed, for sometime now, by systemd so this particular change wouldn't make much sense. IMHO this type of cluster change should be done by the cluster administrator in specific tools like crmsh, pcs, and not in an init script. It is unfortunate that we were unable to resolve this defect, however there appears to be no further action possible at this time. I am therefore moving the bug to 'Incomplete'. If you disagree or have new information, we would be grateful if you could please add a comment stating why and then change the status of the bug to 'New'. ** Also affects: corosync (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: corosync (Ubuntu Precise) Status: New => Incomplete ** Changed in: corosync (Ubuntu) Status: Triaged => Won't Fix ** Changed in: corosync (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: corosync (Ubuntu Precise) Status: Incomplete => Won't Fix ** Changed in: corosync (Ubuntu) Importance: High => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1340172 Title: [OSCI] Add mamange/unmanage blocks to corosync init scripts To manage notifications about this bug go to: https://bugs.launchpad.net/fuel/+bug/1340172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1340172] Re: [OSCI] Add mamange/unmanage blocks to corosync init scripts
Thank you for taking the time to report this bug. In an effort to keep an up-to-date and valid list of bugs to work on, I have reviewed this report to verify it still requires effort and occurs on an Ubuntu release in standard support, and it does not. Unfortunately this bug is old for us to consider having an sysv-compatible option to put the cluster into maintenance mode. Corosync is also being managed, for sometime now, by systemd so this particular change wouldn't make much sense. IMHO this type of cluster change should be done by the cluster administrator in specific tools like crmsh, pcs, and not in an init script. It is unfortunate that we were unable to resolve this defect, however there appears to be no further action possible at this time. I am therefore moving the bug to 'Incomplete'. If you disagree or have new information, we would be grateful if you could please add a comment stating why and then change the status of the bug to 'New'. ** Also affects: corosync (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: corosync (Ubuntu Precise) Status: New => Incomplete ** Changed in: corosync (Ubuntu) Status: Triaged => Won't Fix ** Changed in: corosync (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: corosync (Ubuntu Precise) Status: Incomplete => Won't Fix ** Changed in: corosync (Ubuntu) Importance: High => Undecided -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1340172 Title: [OSCI] Add mamange/unmanage blocks to corosync init scripts To manage notifications about this bug go to: https://bugs.launchpad.net/fuel/+bug/1340172/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1860244] Re: Gdm3 - infinite login
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (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/1860244 Title: Gdm3 - infinite login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1860244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860115] Re: normal usage then all apps stopped working
[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/1860115 Title: normal usage then all apps stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752239] Re: Xorg crash
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (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/1752239 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1752239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850238] Re: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels
As the original reporter, I feel the obligation to reply: I'm not using the problematic laptop anymore, so if anyone else can test the proposed version - that would be most awesome! kaihengfeng, thanks for taking a look! I'm curious - are you in contact with / part of the kernel USB team? Could you link to the commit the version you posted was built from? Testing new kernels is rather time-consuming for me due to lack of experience. Understanding the proposed patch and how it can fix the problem would make it much more fun (especially as the last time I checked - December i think? - the mainline kernel had regressed further on this hardware.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850238 Title: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866903] Re: Autopkgtest regression trigerred by Ruby 2.7
This bug was fixed in the package ruby-fakefs - 0.20.1-2 Sponsored for Lucas Kanashiro (lucaskanashiro) --- ruby-fakefs (0.20.1-2) unstable; urgency=medium * Team upload. * Add patch to add ruby 2.7 support (Closes: #952080) * Declare compliance with Debian Policy 4.5.0 * d/control: rules does not require root * Do not runtime depend on ruby interpreter -- Lucas Kanashiro Thu, 19 Mar 2020 12:57:36 -0300 ** Changed in: ruby-fakefs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866903 Title: Autopkgtest regression trigerred by Ruby 2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-fakefs/+bug/1866903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio
** Changed in: linux (Ubuntu Bionic) Status: New => Won't Fix ** Description changed: + Drop the B, so far only need to merge this patchset to OEM-B first, + After the patchset is widely verified with oem-b kernel, I send the + patchset to B and F then. + + This patchset will add support of mst audio for nvidia hdmi/dp, this patchset changes lots of common code on hda_jack and hdmi codec, so it is not easy to say it is 100% safe for other machines, but our oem project needs this patchset to be backported to ubuntu kernel, because the tight sechdule of oem project, we backport this patchset to B and OEM-B first, if the hdmi audio works well for a period of time after this patchset is merged, I will backport this patchset to focal, maybe eoan as well. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + - LENOVO Docking Gen2 + LENOVO Docking Gen2 [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work. - [Regression Risk] Low, those patches come from mainline kernel, I have tested those patches on the machiens with or without nvidia hdmi, and on the machines with or without docks, all worked well as before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867704 Title: alsa/hdmi: support nvidia mst hdmi/dp audio To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1867704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868198] Re: package grub-efi-amd64-signed 1.128.2+2.04-1ubuntu12.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit stat
Thank you for taking the time to report this issue and helping to make Ubuntu better. In the 'dpkg-terminal-log' output I notice grub-install: error: cannot open `/boot/efi/EFI/ubuntu/grubx64.efi': Read-only file system. In your 'dmesg' output are many errors on a FS that caused the RO trip, ie. [ 93.081833] FAT-fs (sda2): error, corrupted directory (invalid entries) [ 93.081837] FAT-fs (sda2): Filesystem has been set read-only [ 93.082972] FAT-fs (sda2): error, corrupted directory (invalid entries) [ 93.087589] FAT-fs (sda2): error, corrupted directory (invalid entries) [ 93.095266] FAT-fs (sda2): error, corrupted directory (invalid entries) [ 4309.733625] FAT-fs (sda2): error, fat_get_cluster: invalid cluster chain (i_pos 0) [ 4309.733654] FAT-fs (sda2): error, fat_get_cluster: invalid cluster chain (i_pos 0) [ 4309.734815] FAT-fs (sda2): error, fat_get_cluster: invalid cluster chain (i_pos 0) [ 4309.734832] FAT-fs (sda2): error, fat_get_cluster: invalid cluster chain (i_pos 0) [ 4309.739088] FAT-fs (sda2): error, fat_get_cluster: invalid cluster chain (i_pos 0) [ 4309.739111] FAT-fs (sda2): error, fat_get_cluster: invalid cluster chain (i_pos 0) [ 4309.746569] FAT-fs (sda2): error, fat_get_cluster: invalid cluster chain (i_pos 0) [ 4309.746601] FAT-fs (sda2): error, fat_get_cluster: invalid cluster chain (i_pos 0) I suspect your issue isn't bug related, but you've an EFI partition that likely needs a `fsck` to correct file system errors, thus support would be more appropriate, eg. https://answers.launchpad.net/ubuntu . You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org , or for more support options please look at https://discourse.ubuntu.com/t/community- support/709 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868198 Title: package grub-efi-amd64-signed 1.128.2+2.04-1ubuntu12.2 failed to install/upgrade: installed grub-efi-amd64-signed 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-signed/+bug/1868198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] Re: AMD graphics terrible pixelation on XFCE
apport-collect updated and posted below. Again I know this is Linux- Mint, but syncing to ensure there is visibility. I posted in the XFCE and LM forums, and essentially my understanding this is a driver incompatibility or library issue between the amdgpu open source drives in kernel 5.3 and XFCE's Windows Compositor. Disabling windows compositor (vsync) fixes the pixelation, but introduces wicked tearing, while all this was and is fine using 5.0. ** 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/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339156/+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/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868198] [NEW] package grub-efi-amd64-signed 1.128.2+2.04-1ubuntu12.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit st
Public bug reported: ubuntu 19.10 this happened a minute or two after installing updates and about 10 seconds after changing my wallpaper. Not sure if that's helpful ProblemType: Package DistroRelease: Ubuntu 19.10 Package: grub-efi-amd64-signed 1.128.2+2.04-1ubuntu12.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 Date: Thu Mar 19 22:58:26 2020 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-03 (17 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.128.2+2.04-1ubuntu12.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868198 Title: package grub-efi-amd64-signed 1.128.2+2.04-1ubuntu12.2 failed to install/upgrade: installed grub-efi-amd64-signed 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-signed/+bug/1868198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339151/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] Re: AMD graphics terrible pixelation on XFCE
apport information ** Tags added: apport-collected tricia ** Description changed: So posted this on several forums in Linux Mint 19.3 and XFCE. Seems like the major difference is AMD base driver changes from 5.0.0-37 to 5.3 <- thus far any version causes severe pixelation for every new window rendering Linux Mint XFCE unusable unless the Windows Display Compositor is disabled. The hardware is an AMD Ryzen 5-3500U with 8 GB RAM. 5.0.0-37 runs fine, and I installed Ubuntu Gnome desktop which also seems to work (though not as snappy as the original XFCE). I wanted to highlight and also understand if Xubuntu might face a similar issue with that APU come the 20.04 update or if there is a fix that hasn't made it to the Linux Mint distribution. Other posts for reference: https://forums.linuxmint.com/viewtopic.php?t=310609 https://bugzilla.xfce.org/show_bug.cgi?id=16403 Thank you + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.12 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: joe2641 F pulseaudio + /dev/snd/controlC0: joe2641 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Linux Mint 19.3 + EcryptfsInUse: Yes + InstallationDate: Installed on 2020-01-03 (76 days ago) + InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 + MachineType: LENOVO 81NB + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=9608f780-6ba5-4994-a7dc-72fa01f3daf5 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-42-generic N/A + linux-backports-modules-5.3.0-42-generic N/A + linux-firmware1.173.16 + Tags: tricia + Uname: Linux 5.3.0-42-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/15/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: AMCN26WW(V1.09) + dmi.board.asset.tag: NO Asset Tag + dmi.board.name: LNVNB161216 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40700 WIN + dmi.chassis.asset.tag: NO Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Lenovo IdeaPad S340-14API + dmi.modalias: dmi:bvnLENOVO:bvrAMCN26WW(V1.09):bd11/15/2019:svnLENOVO:pn81NB:pvrLenovoIdeaPadS340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14API: + dmi.product.family: IdeaPad S340-14API + dmi.product.name: 81NB + dmi.product.sku: LENOVO_MT_81NB_BU_idea_FM_IdeaPad S340-14API + dmi.product.version: Lenovo IdeaPad S340-14API + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339145/+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/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339154/+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/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339159/+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/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339157/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339146/+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/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339158/+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/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339147/+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/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339150/+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/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339153/+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/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339149/+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/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339152/+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/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339155/+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/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868091] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1868091/+attachment/5339148/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868091 Title: AMD graphics terrible pixelation on XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868197] 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/1868197 Title: iwlwifi fails to communicate with Intel Wireless-AC 9650 card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868196] 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/1868196 Title: HID ELAN9038 probe fails with "report is too long" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868197] [NEW] iwlwifi fails to communicate with Intel Wireless-AC 9650 card
Public bug reported: This isn't a bug just in the Ubuntu kernel, as it happened on Debian too, and I wouldn't rule out any hardware issue either, but I wanted to share this here to see if I could get any help. I dual boot Windows and Linux and I think my WiFi card might be failing, but it could also be a case of bad firmware. It used to work well, but now both Windows and Linux fail to start my card most of the time. However, sometimes Windows will successfully be able to use it. This is the latest bit of error lines that have appeared in dmesg: [8.109230] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [8.521736] [ cut here ] [8.521737] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c) [8.521772] WARNING: CPU: 4 PID: 487 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2015 iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [8.521772] Modules linked in: cmac bnep snd_hda_codec_hdmi nls_iso8859_1 sof_pci_dev snd_sof_intel_hda_common snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_soc_skl snd_hda_codec_realtek snd_soc_hdac_hda snd_hda_codec_generic ledtrig_audio snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine x86_pkg_temp_thermal intel_powerclamp joydev coretemp kvm_intel kvm irqbypass snd_hda_intel snd_intel_nhlt snd_hda_codec mei_hdcp snd_hda_core intel_rapl_msr snd_hwdep snd_pcm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_seq_midi snd_seq_midi_event snd_rawmidi aesni_intel nouveau snd_seq snd_seq_device iwlmvm aes_x86_64 crypto_simd ttm cryptd asus_nb_wmi snd_timer i915 glue_helper intel_cstate mac80211 uvcvideo videobuf2_vmalloc input_leds drm_kms_helper intel_rapl_perf serio_raw wmi_bmof libarc4 btusb videobuf2_memops btrtl videobuf2_v4l2 btbcm btintel [8.521786] hid_sensor_accel_3d asus_wmi videobuf2_common snd mxm_wmi bluetooth hid_sensor_trigger industrialio_triggered_buffer kfifo_buf drm hid_sensor_iio_common videodev industrialio iwlwifi i2c_algo_bit fb_sys_fops soundcore mc mei_me syscopyarea ecdh_generic processor_thermal_device ecc cros_ec_ishtp idma64 hid_multitouch intel_rapl_common cros_ec_core virt_dma sysfillrect intel_pch_thermal intel_soc_dts_iosf sysimgblt mei cfg80211 int3403_thermal int340x_thermal_zone intel_hid int3400_thermal acpi_thermal_rel mac_hid sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid hid_generic nvme nvme_core i2c_i801 ahci intel_lpss_pci intel_ish_ipc i2c_hid libahci intel_lpss intel_ishtp hid pinctrl_cannonlake wmi video pinctrl_intel [8.521801] CPU: 4 PID: 487 Comm: irq/146-iwlwifi Tainted: GW 5.3.0-42-generic #34-Ubuntu [8.521801] Hardware name: ASUSTeK COMPUTER INC. ZenBook Q536FD_Q536FD/Q536FD, BIOS Q536FD.306 05/31/2019 [8.521806] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi] [8.521807] Code: fa da 49 8d 57 08 bf 00 20 00 00 e8 c1 4f 81 d9 e9 30 ff ff ff 89 c6 48 c7 c7 58 f5 6c c0 c6 05 81 11 03 00 01 e8 e2 51 7f d9 <0f> 0b e9 eb fe ff ff 49 8b 7c 24 30 48 c7 c1 c0 f5 6c c0 31 d2 31 [8.521807] RSP: 0018:aee380b8bc98 EFLAGS: 00010082 [8.521808] RAX: RBX: aee380b8bcd0 RCX: 0006 [8.521808] RDX: 0007 RSI: 0082 RDI: 9422dbb17440 [8.521809] RBP: aee380b8bcc0 R08: 0469 R09: 0004 [8.521809] R10: R11: 0001 R12: 9422d3670018 [8.521809] R13: R14: 9422d36790b4 R15: 0c04000c [8.521810] FS: () GS:9422dbb0() knlGS: [8.521810] CS: 0010 DS: ES: CR0: 80050033 [8.521811] CR2: 557d76a01338 CR3: 0002f2e0a003 CR4: 003606e0 [8.521811] Call Trace: [8.521817] iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi] [8.521822] iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm] [8.521825] ? __dev_printk+0x5c/0x6f [8.521826] ? _dev_err+0x6c/0x83 [8.521827] ? lock_timer_base+0x72/0xa0 [8.521831] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [8.521834] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [8.521838] iwl_pcie_irq_handle_error+0xb1/0x110 [iwlwifi] [8.521841] iwl_pcie_irq_msix_handler+0x197/0x4b0 [iwlwifi] [8.521843] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [8.521844] irq_thread_fn+0x28/0x60 [8.521845] irq_thread+0xda/0x170 [8.521845] ? irq_forced_thread_fn+0x80/0x80 [8.521847] kthread+0x104/0x140 [8.521848] ? irq_thread_check_affinity+0xf0/0xf0 [8.521849] ? kthread_park+0x80/0x80 [8.521851] ret_from_fork+0x35/0x40 [8.521852] ---[ end trace 8398d136a219cba4 ]--- [8.521853] iwlwifi :00:14.3: iwlwifi
[Bug 1868196] [NEW] HID ELAN9038 probe fails with "report is too long"
Public bug reported: As of upgrade to kernel 5.3.0-42 I see errors in journal reported for ELAN9038 HID. $ uname -a Linux 5.3.0-42-generic #34-Ubuntu SMP Fri Feb 28 05:49:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ sudo journalctl -b | grep multitouch hid-multitouch 0018:04F3:261A.0001: report is too long hid-multitouch 0018:04F3:261A.0001: item 0 1 0 8 parsing failed hid-multitouch: probe of 0018:04F3:261A.0001 failed with error -22 The same device on 5.3.0-40 works without issues. $ uname -a Linux 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ sudo journalctl -b | grep multitouch hid-multitouch 0018:04F3:261A.0001: input,hidraw0: I2C HID v1.00 Device [ELAN9038:00 04F3:261A] on i2c-ELAN9038:00 I did find the same issue has been also reported on version 5.6 under bug #206259 (https://bugzilla.kernel.org/show_bug.cgi?id=206259). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-42-generic 5.3.0-42.34 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josip 3946 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 19:36:40 2020 InstallationDate: Installed on 2020-03-08 (11 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 045e:096f Microsoft Corp. Surface Type Cover Bus 001 Device 002: ID 0cf3:e302 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Go 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=/vmlinuz-5.3.0-42-generic root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 1.0.19 dmi.board.name: Surface Go dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnMicrosoftCorporation:bvr1.0.19:bd06/24/2019:svnMicrosoftCorporation:pnSurfaceGo:pvr1:rvnMicrosoftCorporation:rnSurfaceGo:rvr:cvnMicrosoftCorporation:ct9:cvrChassisVersion: dmi.product.family: Surface dmi.product.name: Surface Go dmi.product.sku: Surface_Go_1824_Consumer dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868196 Title: HID ELAN9038 probe fails with "report is too long" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868131] Re: Integrated speakers always muted
** This bug is no longer a duplicate of bug 1310121 headphones working while speakers not working ** Summary changed: - Integrated speakers always muted + [Toshiba NB250] Integrated speakers always muted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868131 Title: [Toshiba NB250] Integrated speakers always muted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868155] Re: Banner text and user list functionality seem broken
I'm not familiar with this feature but do know the GUI is provided by the gnome-shell process so the bug should be reported there. Please report the issue upstream at: https://gitlab.gnome.org/GNOME/gnome-shell/issues and then tell us the new bug ID. ** Package changed: gdm3 (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/1868155 Title: Banner text and user list functionality seem broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868128] Re: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24)
Firstly, not related to this bug but I notice your system will be running very slow because it's logging every single screen refresh to the kernel log. To stop that you should remove the kernel parameter: drm.debug=0xe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868128 Title: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1868128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868128] Re: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24)
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1868128 Title: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1868128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868083] Re: gnome-shell process "estabilished"
For some of us we may just need: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1100 and don't necessarily need to wait for: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1099 ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Summary changed: - gnome-shell process "estabilished" + gnome-shell establishes https connections to extensions.gnome.org ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868083 Title: gnome-shell establishes https connections to extensions.gnome.org To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864061] Re: PCI/internal sound card not detected
Akkana, Could you upload your dmesg, or could you install 5.3.0-43 kernel, and with -43 kernel, you could remove dmic_detect=0 or keep it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864061 Title: PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867758] Re: Gnome shell froze completely
If a crash has been uploaded then please tell us the resulting new bug ID. If you don't know it then try uploading using something like this command: apport-cli YOURFILE.crash And if that doesn't work then please delete /var/crash/* and wait for it to happen again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867758 Title: Gnome shell froze completely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865379] Re: Raspberry Pi 4 fails to wake at login prompt
Error report links are public unless you feel something particularly personal has been shown on that page. So please paste the link here. And if you prefer you can change this bug page to Private using the setting at the top right of this page. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865379 Title: Raspberry Pi 4 fails to wake at login prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867398] Re: [Regression] unsupported protocol scheme
** Patch added: "Bionic debdiff" https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1867398/+attachment/5339108/+files/fix-1867398-bionic.debdiff ** Changed in: containerd (Ubuntu Focal) Status: New => Fix Released ** Changed in: containerd (Ubuntu Eoan) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867398 Title: [Regression] unsupported protocol scheme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1867398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867398] Re: [Regression] unsupported protocol scheme
Attached is the debdiff that fixes this problem in bionic, it's a backport of commit [0] [0] https://github.com/containerd/containerd/commit/a022c218194c05449ad69b69c48fc6cac9d6f0b3 ** Tags added: sts-needs-sponsor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867398 Title: [Regression] unsupported protocol scheme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1867398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868009] Re: Xorg high CPU usage and stuttering with the Nvidia driver
It's probably a loose or poor quality HDMI connection so try a different cable to the same TV. Or try the same cable to a different TV. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868009 Title: Xorg high CPU usage and stuttering with the Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1868009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868192] Re: Error message claiming the USB disk is faulty
Thank you for taking the time to report this issue and helping to make Ubuntu better. This package failure looks like it was caused by bad ISO download, corrupted install media, or device failure. eg. look in the logs and you'll see messages like these :- Mar 20 01:47:12 ubuntu kernel: [ 287.305056] SQUASHFS error: zlib decompression failed, data probably corrupt Mar 20 01:47:12 ubuntu kernel: [ 287.305058] SQUASHFS error: squashfs_read_data failed to read block 0x2003b90e Examining the information you have given us, this does not appear to be a useful bug report so I am closing it, as it appears to be a bad ISO or faulty device (inc. bad write-to-device). If you believe I'm in error, please leave a comment explaining why and change the status back to 'New'. I suggest you verify your ISO download, and use the 'check disc for defects' option to validate your media before install to ensure a good download & write. Possibly useful : https://tutorials.ubuntu.com/tutorial/tutorial-how-to- verify-ubuntu#0 and https://help.ubuntu.com/community/Installation/CDIntegrityCheck (where CD refers to your install media, be it CD, DVD, HDD, SSD, thumb-drive etc) ** Changed in: ubiquity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868192 Title: Error message claiming the USB disk is faulty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1868192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868191] Re: Unchecking all optional media apps, install fails
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1868191 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868191 Title: Unchecking all optional media apps, install fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1868191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868192] [NEW] Error message claiming the USB disk is faulty
Public bug reported: Error message claiming the USB disk is faulty ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.6 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CasperVersion: 1.441 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 12:47:27 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200318) ProcEnviron: LANGUAGE=en_AU.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug focal ubiquity-20.04.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868192 Title: Error message claiming the USB disk is faulty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1868192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868191] [NEW] Unchecking all optional media apps, install fails
Public bug reported: ISO testing 20.04 Studio's daily image (20200319). A screen appears with about a dozen various media/photography apps which are checkmarked. I am invited to uncheck any or all. I unchecked all. The install fails near the end. There is an "oopsie" msg which disappears, and the installation ends. When I reboot, I'm dropped at a command-line login. I saw this with yesterday's daily image too. But, I haven't tried this before. It could have always been this way. FWIW: unchecking all those media apps results in the installation taking 3-4 times longer. I expected it to install very fast. It never does complete. The progress bar is about 4/5ths of the way to the right edge, and then the oopsie msg occurs. I Ubuiquity disappears after that. It seems to be removing packages for a long time when this happens. Maybe nobody would ever uncheck all. It's probably not an important problem. I just wanted to bring it to someone's attention. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.6 ProcVersionSignature: Ubuntu 5.4.0-18.22-lowlatency 5.4.24 Uname: Linux 5.4.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CasperVersion: 1.441 CurrentDesktop: XFCE Date: Fri Mar 20 01:23:11 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntustudio.seed quiet splash --- LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200319) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntustudio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868191 Title: Unchecking all optional media apps, install fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1868191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@eddie, If your usb audio doesn't work, please file a new bug against the linux kernel. Let's track your issue in that bug. thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868189] [NEW] Low memory situations result in root partition being remounted read-only
Public bug reported: Instead of killing something with a high niceness low memory situations seem to hang something super-ultra-so-very vital, writes fail and the root partition is remounted read-only. After that systemd-journald starts stupidly spamming and earlier logs are rendered unusable. I'd post more logs but https://github.com/systemd/systemd/issues/2339 hasn't been fixed in years. This has happened at least four times, across many kernel versions. With Ubuntu 18.10, 19.04 and 19.10. ``` [827788.409138] sd 5:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409141] sd 5:0:0:0: [sdb] tag#12 CDB: Write(10) 2a 00 01 e0 b8 f0 00 00 10 00 [827788.409143] blk_update_request: I/O error, dev sdb, sector 31504624 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [827788.409151] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871518) [827788.409154] Buffer I/O error on device dm-1, logical block 3871518 [827788.409163] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871519) [827788.409164] Buffer I/O error on device dm-1, logical block 3871519 [827788.409172] sd 5:0:0:0: [sdb] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409174] sd 5:0:0:0: [sdb] tag#11 CDB: Write(10) 2a 00 01 e0 bb 70 00 00 08 00 [827788.409175] blk_update_request: I/O error, dev sdb, sector 31505264 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409179] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871598) [827788.409180] Buffer I/O error on device dm-1, logical block 3871598 [827788.409188] sd 5:0:0:0: [sdb] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409189] sd 5:0:0:0: [sdb] tag#10 CDB: Write(10) 2a 00 01 e0 ba 60 00 00 38 00 [827788.409190] blk_update_request: I/O error, dev sdb, sector 31504992 op 0x1:(WRITE) flags 0x0 phys_seg 7 prio class 0 [827788.409194] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871564) [827788.409195] Buffer I/O error on device dm-1, logical block 3871564 [827788.409196] Buffer I/O error on device dm-1, logical block 3871565 [827788.409198] Buffer I/O error on device dm-1, logical block 3871566 [827788.409199] Buffer I/O error on device dm-1, logical block 3871567 [827788.409201] Buffer I/O error on device dm-1, logical block 3871568 [827788.409202] Buffer I/O error on device dm-1, logical block 3871569 [827788.409203] Buffer I/O error on device dm-1, logical block 3871570 [827788.409210] sd 5:0:0:0: [sdb] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409211] sd 5:0:0:0: [sdb] tag#9 CDB: Write(10) 2a 00 01 e0 ba 30 00 00 08 00 [827788.409212] blk_update_request: I/O error, dev sdb, sector 31504944 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409216] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871558) [827788.409220] sd 5:0:0:0: [sdb] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409221] sd 5:0:0:0: [sdb] tag#8 CDB: Write(10) 2a 00 01 e0 ba 50 00 00 08 00 [827788.409222] blk_update_request: I/O error, dev sdb, sector 31504976 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409225] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871562) [827788.409228] sd 5:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409229] sd 5:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 01 e0 bb 88 00 00 08 00 [827788.409230] blk_update_request: I/O error, dev sdb, sector 31505288 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409233] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871601) [827818.628273] sd 5:0:0:0: [sdb] tag#31 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827818.628276] sd 5:0:0:0: [sdb] tag#31 CDB: Write(10) 2a 00 01 cf 12 38 00 00 30 00 [827818.628279] blk_update_request: I/O error, dev sdb, sector 30347832 op 0x1:(WRITE) flags 0x800 phys_seg 6 prio class 0 [827818.628347] sd 5:0:0:0: [sdb] tag#28 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827818.628351] sd 5:0:0:0: [sdb] tag#28 CDB: Write(10) 2a 00 01 93 2f b0 00 00 08 00 [827818.628353] blk_update_request: I/O error, dev sdb, sector 26423216 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827818.628358] Aborting journal on device dm-1-8. [827818.628374] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3236342) [827818.628379] buffer_io_error: 3 callbacks suppressed [827818.628381] Buffer I/O error on device dm-1,
[Bug 1868152] Re: geary won't start after upgrading to 3.36
fwiw, here's gdb backtrace when seeing this bug: (gdb) bt #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x77d74483 in g_cond_wait () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x77d50b0f in g_once_init_enter () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fff8ca5370c in plugin_notification_get_type () at /usr/lib/x86_64-linux-gnu/geary/plugins/messaging-menu/libmessaging-menu-geary.so #4 0x7fff8c980e07 in peas_register_types () at /usr/lib/x86_64-linux-gnu/geary/plugins/messaging-menu/libmessaging-menu-geary.so #5 0x759d34cc in () at /lib/x86_64-linux-gnu/libpeas-1.0.so.0 #6 0x77e3c58b in g_type_module_use () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x759d5d9b in () at /lib/x86_64-linux-gnu/libpeas-1.0.so.0 #8 0x759cf9e0 in () at /lib/x86_64-linux-gnu/libpeas-1.0.so.0 #9 0x77e12802 in g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x77e25f96 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x77e31b9e in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x77e32b7c in g_signal_emit_by_name () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 --Type for more, q to quit, c to continue without paging--c #13 0x55633d09 in application_plugin_manager_load () #14 0x55606c50 in () #15 0x555f856c in () #16 0x7787ae79 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #17 0x7787aebd in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #18 0x77d26e8e in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x77d27240 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x77d272e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x778a8f05 in g_application_run () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #22 0x555f4d67 in _vala_main () #23 0x722aa0b3 in __libc_start_main (main=0x555f4bc0 , argc=1, argv=0x7fffdaa8, init=, fini=, rtld_fini=, stack_end=0x7fffda98) at ../csu/libc-start.c:308 #24 0x555f4c0e in _start () Also, I only get the first 3 lines of log output above, nothing about GearyBaseObject etc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868152 Title: geary won't start after upgrading to 3.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geary/+bug/1868152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922858] Re: no icon visual in unity and unity 2d
This was fixed in 20140331-1. ** Changed in: qxw (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922858 Title: no icon visual in unity and unity 2d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qxw/+bug/922858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868187] Re: [FFe] Sync version 15.8.25.3.gcf41df6a2-6 from Debian unstable
FFe approved, if you can get the NEW packages through in time. ** Changed in: chef (Ubuntu) Status: New => Confirmed ** Changed in: chef (Ubuntu) Importance: Undecided => Medium ** Also affects: ohai (Ubuntu) Importance: Undecided Status: New ** Also affects: ruby-cheffish (Ubuntu) Importance: Undecided Status: New ** Also affects: ruby-mixlib-authentication (Ubuntu) Importance: Undecided Status: New ** Also affects: ruby-mixlib-cli (Ubuntu) Importance: Undecided Status: New ** Also affects: ruby-mixlib-config (Ubuntu) Importance: Undecided Status: New ** Also affects: ruby-mixlib-log (Ubuntu) Importance: Undecided Status: New ** Also affects: ruby-mixlib-shellout (Ubuntu) Importance: Undecided Status: New ** Changed in: ohai (Ubuntu) Status: New => Confirmed ** Changed in: ruby-cheffish (Ubuntu) Status: New => Incomplete ** Changed in: ruby-cheffish (Ubuntu) Status: Incomplete => Confirmed ** Changed in: ruby-mixlib-authentication (Ubuntu) Status: New => Confirmed ** Changed in: ruby-mixlib-cli (Ubuntu) Status: New => Confirmed ** Changed in: ruby-mixlib-config (Ubuntu) Status: New => Confirmed ** Changed in: ruby-mixlib-log (Ubuntu) Status: New => Confirmed ** Changed in: ruby-mixlib-shellout (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/1868187 Title: [FFe] Sync version 15.8.25.3.gcf41df6a2-6 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chef/+bug/1868187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922858] Re: no icon visual in unity and unity 2d
** Bug watch added: Debian Bug tracker #738014 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738014 ** Also affects: qxw (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738014 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922858 Title: no icon visual in unity and unity 2d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qxw/+bug/922858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
The kernel 5.3.0-43 is in the -proposed, please use this kernel instead of -42 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868152] Re: geary won't start after upgrading to 3.36
@jbicha does this ring any bells? I'd really rather Ubuntu not ship a version of Geary that does not start. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868152 Title: geary won't start after upgrading to 3.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geary/+bug/1868152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868187] [NEW] [FFe] Sync version 15.8.25.3.gcf41df6a2-6 from Debian unstable
Public bug reported: Current version of chef in the archive (13.8.7-6) is broken and it is not working with Ruby 2.7. In Debian, a new upstream version was uploaded which supports Ruby 2.7 and the maintainer has performed some tests to make sure it is working fine. There current Debian version is 15.8.25.3.gcf41df6a2-6 and it contains many changes made by upstream compared to the version in Ubuntu since this is a major version bump. However, the Ubuntu version is not working with Ruby 2.7 so there is no risk to get it worse. The diff of the upstream changelog is attached. To sync this Debian release we also need to update some chef's dependencies: * chef-zero/15.0.0-2 -> current version in Ubuntu: 13.1.0-2 * ohai/16.0.7-3 -> current version in Ubuntu: 13.8.0-1 - There is a circular dependency between src:ohai and src:chef) * ruby-cheffish/15.0.1-1 -> current version in Ubuntu: 13.1.0-2 * ruby-mixlib-authentication/3.0.6-1 -> current version in Ubuntu: 1.4.1-1 * ruby-mixlib-cli/2.1.6-1 -> current version in Ubuntu: 1.7.0-1 * ruby-mixlib-config/3.0.6-1 -> current version in Ubuntu: 2.2.6-1 * ruby-mixlib-log/3.0.8-1 -> current version in Ubuntu: 1.7.1-1 - There is a sync request for it: https://bugs.launchpad.net/ubuntu/+source/ruby-mixlib-log/+bug/1866390 * ruby-mixlib-shellout/3.0.9-1 -> current version in Ubuntu: 2.2.6-1 And we also need 2 new packages: * ruby-ffi-libarchive/1.0.0+-2 * ruby-train/3.2.20-2 I have prepared a PPA with all those dependencies in it: https://launchpad.net/~lucaskanashiro/+archive/ubuntu/focal-chef- ffe/+packages I created a clean Ubuntu focal amd64 container and installed chef from the PPA above and it worked fine: # apt install -y chef Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libapt-pkg5.90 libfreetype6 libicu65 Use 'apt autoremove' to remove them. The following additional packages will be installed: chef-bin chef-zero libyajl-dev libyajl2 ohai ruby-addressable ruby-bcrypt-pbkdf ruby-bundler ruby-chef-config ruby-chef-utils ruby-diff-lcs ruby-ed25519 ruby-erubis ruby-ffi ruby-ffi-libarchive ruby-ffi-yajl ruby-fuzzyurl ruby-hashie ruby-highline ruby-iniparse ruby-ipaddress ruby-json ruby-mixlib-archive ruby-mixlib-authentication ruby-mixlib-cli ruby-mixlib-config ruby-mixlib-log ruby-mixlib-shellout ruby-molinillo ruby-net-http-persistent ruby-net-scp ruby-net-sftp ruby-net-ssh ruby-net-ssh-gateway ruby-net-ssh-multi ruby-plist ruby-proxifier ruby-public-suffix ruby-rack ruby-syslog-logger ruby-systemu ruby-thor ruby-tomlrb ruby-train-core ruby-tty-screen ruby-uuidtools The following NEW packages will be installed: chef chef-bin chef-zero libyajl-dev libyajl2 ohai ruby-addressable ruby-bcrypt-pbkdf ruby-bundler ruby-chef-config ruby-chef-utils ruby-diff-lcs ruby-ed25519 ruby-erubis ruby-ffi ruby-ffi-libarchive ruby-ffi-yajl ruby-fuzzyurl ruby-hashie ruby-highline ruby-iniparse ruby-ipaddress ruby-json ruby-mixlib-archive ruby-mixlib-authentication ruby-mixlib-cli ruby-mixlib-config ruby-mixlib-log ruby-mixlib-shellout ruby-molinillo ruby-net-http-persistent ruby-net-scp ruby-net-sftp ruby-net-ssh ruby-net-ssh-gateway ruby-net-ssh-multi ruby-plist ruby-proxifier ruby-public-suffix ruby-rack ruby-syslog-logger ruby-systemu ruby-thor ruby-tomlrb ruby-train-core ruby-tty-screen ruby-uuidtools 0 upgraded, 47 newly installed, 0 to remove and 0 not upgraded. Need to get 2402 kB of archives. After this operation, 14.1 MB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal/universe amd64 ruby-tomlrb all 1.2.9-1 [7812 B] Get:2 http://archive.ubuntu.com/ubuntu focal/universe amd64 ruby-fuzzyurl all 0.8.0-1 [7114 B] Get:3 http://archive.ubuntu.com/ubuntu focal/universe amd64 ruby-public-suffix all 3.0.3+ds-1 [13.0 kB] Get:4 http://archive.ubuntu.com/ubuntu focal/universe amd64 ruby-addressable all 2.7.0-1 [47.7 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 ruby-json amd64 2.3.0+dfsg-1build1 [44.6 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 ruby-bcrypt-pbkdf amd64 1.0.1-1build1 [18.5 kB] Get:7 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 ruby-ed25519 amd64 1.2.4-1build1 [59.0 kB] Get:8 http://archive.ubuntu.com/ubuntu focal/universe amd64 ruby-net-ssh all 1:5.2.0-1 [93.1 kB] Get:9 http://archive.ubuntu.com/ubuntu focal/universe amd64 ruby-net-scp all 2.0.0-3 [16.1 kB] Get:10 http://archive.ubuntu.com/ubuntu focal/universe amd64 ruby-mixlib-archive all 0.4.1-1 [5070 B] Get:11 http://archive.ubuntu.com/ubuntu focal/universe amd64 ruby-systemu all 2.6.5-1 [8806 B] Get:12 http://archive.ubuntu.com/ubuntu focal/main amd64 libyajl2 amd64 2.1.0-3 [20.1 kB] Get:13 http://archive.ubuntu.com/ubuntu focal/main amd64 libyajl-dev amd64 2.1.0-3 [26.1 kB] Get:14 http://archive.ubuntu.com/ubuntu
[Bug 1868188] [NEW] FFe: Sync sparql-wrapper-python 1.8.5-1 (universe) from Debian unstable (main)
Public bug reported: Please sync sparql-wrapper-python 1.8.5-1 (universe) from Debian unstable (main) Explanation of FeatureFreeze exception: Removes Python 2 support (and consequently a dependency on python-rdflib), which will then allow us to sync the new rdflib that removes Python 2 support. Builds properly in a Focal pbuilder. Upstream changes since 1.8.2: 2019-12-22 1.8.5 - - Improve/tests for development (#131) - Changed. Be more strict on Accept Turtle header (#137) - Migrated documentation from epydoc to sphinx and readthedocs 2019-04-18 1.8.4 - - Added example - hotfix: Added custom_fixers folder in MANIFEST, in order to be used in python3 (#129) 2019-04-17 1.8.3 - - Include ChangeLog.txt in the distribution - Removed import of SPARQLWrapper in setup.py (fixed #113 and closed #115) - Added support for querying RDF/XML in a CONSTRUCT query type - Updated the procedure for determining the query type (#120) - Do not send format parameter for the results ([format, output, results]) when the query is a SPARQL Update query - Added test for new agrovoc SPARQL endpoint (using Fuseki2) - Added test for 4store SPARQL endpoint (used by agroportal) - Added/Updated tests - Added examples - Updated doc - Fixed code generated for python3 using 2to3, adding a custom fixer (#109) Changelog entries since current focal version 1.8.2-0.1build1: sparql-wrapper-python (1.8.5-1) unstable; urgency=medium [ Emmanuel Arias ] * Team upload * New upstream version 1.8.5 * Remove Python 2 support (Closes: #938523) * Remove patches already applied on upstream [ Ondřej Nový ] * Convert git repository from git-dpm to gbp layout. * Bump Standards-Version to 4.4.0. * Bump Standards-Version to 4.4.1. [ Sandro Tosi ] * complete removal of python2 support * debian/rules - skip tests, they require network access * debian/python3-sparqlwrapper.docs - install README.rst -- Sandro Tosi Mon, 16 Mar 2020 02:33:25 -0400 ** Affects: sparql-wrapper-python (Ubuntu) Importance: Wishlist Status: New ** Changed in: sparql-wrapper-python (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868188 Title: FFe: Sync sparql-wrapper-python 1.8.5-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sparql-wrapper-python/+bug/1868188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868152] Re: geary won't start after upgrading to 3.36
Pretty sure this is a build bug - it doesn't happen when compiling 3.36 from source and running it from there, doesn't happen installing the Debian 3.36.0-2 package either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868152 Title: geary won't start after upgrading to 3.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geary/+bug/1868152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868176] Re: screengrab does not take screenshots from second monitor get black image only
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: screengrab (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/1868176 Title: screengrab does not take screenshots from second monitor get black image only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screengrab/+bug/1868176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868176] Re: screengrab does not take screenshots from second monitor get black image only
It's behaving strange for me too guiverc@d960-ubu2:/de2900/lubuntu_64$ apt-cache policy screengrab screengrab: Installed: 2.0.0-1 It appears to want to take a photo of the middle of my second monitor (not the window), however I got the following when trying to take a photo of my 'hexchat' window on my primary display (see attached) Taking a picture of FULL SCREEN (both displays) looked correct. ** Attachment added: "thankfully my screen does NOT look like this; window (hexchat on primary display)" https://bugs.launchpad.net/ubuntu/+source/screengrab/+bug/1868176/+attachment/5339082/+files/screen-2020-03-20-10-36-50.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868176 Title: screengrab does not take screenshots from second monitor get black image only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screengrab/+bug/1868176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]
fwiw, that patch (or at least a slightly modified version which applies on the Ubuntu 18.04 libappindicator) appears to fix the Discord segfaults for me, and also looks correct from my reading of the gobject documentation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867996 Title: Segfault in app_indicator_set_icon_full [patch attached] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1867996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868184] Re: sng requires rgb.txt
Thanks for the report. It's already fixed in 1.1.0-3 (available in focal fossa). ** Changed in: sng (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868184 Title: sng requires rgb.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sng/+bug/1868184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868179] Re: Typing in virtualbox during installation does not work
Thank you for taking the time to report this bug and helping to make Ubuntu better. I suspect a Support site would be more appropriate, eg. for Ubuntu you can use https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 Please note your issue I suspect relates to configuration/settings on your HOST OS which will be off-topic on many Ubuntu sites. The fact that it impacts all ISOs you mention also increases weight on it the common cause, possibly your vbox config/settings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868179 Title: Typing in virtualbox during installation does not work To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1868179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860425] Re: Manually installed deb package cannot be uninstalled
Upstream gnome-software issue: https://gitlab.gnome.org/GNOME/gnome- software/issues/912 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/issues #912 https://gitlab.gnome.org/GNOME/gnome-software/issues/912 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860425 Title: Manually installed deb package cannot be uninstalled To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1860425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864307] Re: Many apps have no icon in Software on Focal
Also seems to happen in Snap Store. ** Also affects: snap-store 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/1864307 Title: Many apps have no icon in Software on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1864307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868184] [NEW] sng requires rgb.txt
Public bug reported: After writing the IHDR segment, sng fails with "RGB database /usr/share/X11/rgb.txt is missing." I assume this wasn't noticed because it is only an issue on systems without X11; the package should depend on x11-common. ** Affects: sng (Ubuntu) Importance: Undecided Status: New ** Description changed: - After writing the IHDR file, sng fails with "RGB database + After writing the IHDR segment, sng fails with "RGB database /usr/share/X11/rgb.txt is missing." I assume this wasn't noticed because it is only an issue on systems without X11; the package should depend on x11-common. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868184 Title: sng requires rgb.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sng/+bug/1868184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865536] Re: OBS consumes all memory, fixed in upstream Mesa
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (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/1865536 Title: OBS consumes all memory, fixed in upstream Mesa To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1865536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867187] Re: Geary 3.35.90-3 - No UI, but System Monitor Lists Process
*** This bug is a duplicate of bug 1868152 *** https://bugs.launchpad.net/bugs/1868152 ** This bug has been marked a duplicate of bug 1868152 geary won't start after upgrading to 3.36 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867187 Title: Geary 3.35.90-3 - No UI, but System Monitor Lists Process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geary/+bug/1867187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868152] Re: geary won't start after upgrading to 3.36
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: geary (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/1868152 Title: geary won't start after upgrading to 3.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geary/+bug/1868152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865536] Re: OBS consumes all memory, fixed in upstream Mesa
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865536 Title: OBS consumes all memory, fixed in upstream Mesa To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1865536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373919] Re: Can't paste images into compose window
This was fixed in 3.36 ** Changed in: geary (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373919 Title: Can't paste images into compose window To manage notifications about this bug go to: https://bugs.launchpad.net/geary/+bug/1373919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867970] Re: Gnome WiFi Settings Freeze
Reported upstream at: https://gitlab.gnome.org/GNOME/gnome-control- center/issues/928 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #928 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/928 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867970 Title: Gnome WiFi Settings Freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1867970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860013] Re: [thunderx] Synchronous External Abort: synchronous parity or ECC error
@Juery: I have no reason to believe this is related to the boot regression we fixed (bug 1857074). I haven't re-tested lately, but as of 4.15.0-76 it was still reproducible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860013 Title: [thunderx] Synchronous External Abort: synchronous parity or ECC error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860013] Re: [thunderx] Synchronous External Abort: synchronous parity or ECC error
sorry s/Juery/Juerg/! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860013 Title: [thunderx] Synchronous External Abort: synchronous parity or ECC error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868083] Re: gnome-shell process "estabilished"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (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/1868083 Title: gnome-shell process "estabilished" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868009] Re: Xorg high CPU usage and stuttering with the Nvidia driver
I can confirm that unplugging my TCL TV HDMI connection gets rid of the problem. How strange that it would be reconnecting multiple times per second. Any thoughts on why or how to proceed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868009 Title: Xorg high CPU usage and stuttering with the Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1868009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866659] Re: Xubuntu 20.04 has incomplete language support of offline install
Sorry, that would've been useful info. English (US). I haven't tested a recent daily build,so I don't know if this is still a problem or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866659 Title: Xubuntu 20.04 has incomplete language support of offline install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1866659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867515] Re: [xubuntu] logo doesnt appear on first page
** Changed in: ubiquity (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867515 Title: [xubuntu] logo doesnt appear on first page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1867515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867970] Re: Gnome WiFi Settings Freeze
Thank you for your bug report, could you report the issue upstream as well on https://gitlab.gnome.org/GNOME/gnome-control-center/issues ? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867970 Title: Gnome WiFi Settings Freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1867970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1866932] Re: package snapd 2.44~pre1+20.04 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866932 Title: package snapd 2.44~pre1+20.04 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1866932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@hui.wang My USB headset no longer works. I installed kernel 5.3.0-43 from proposed and libasound2 from your ppa. $ uname -a Linux eddie-minut 5.3.0-43-generic #36-Ubuntu SMP Mon Mar 16 13:29:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ cat /sys/devices/virtual/dmi/id/bios_version N2HET46W (1.29 ) $ dpkg -l libasound2 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=-- ii libasound2:amd64 1.1.9-0ubuntu1.2++testucm amd64shared library for ALSA applications $ dmesg ... [ 464.139786] usb 1-3: Manufacturer: Kingston [ 464.378226] input: Kingston HyperX Cloud Flight Wireless Headset Consumer Control as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input33 [ 464.437214] input: Kingston HyperX Cloud Flight Wireless Headset as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input34 [ 464.437594] input: Kingston HyperX Cloud Flight Wireless Headset as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input35 [ 464.437943] input: Kingston HyperX Cloud Flight Wireless Headset as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input36 [ 464.438711] hid-generic 0003:0951:16C4.0005: input,hiddev0,hidraw1: USB HID v1.11 Device [Kingston HyperX Cloud Flight Wireless Headset] on usb-:00:14.0-3/input3 [ 465.169150] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 465.264582] sof-audio-pci :00:1f.3: firmware boot complete [ 465.578000] debugfs: File 'Analog Playback and Capture' in directory 'HDA Analog' already present! [ 465.703404] debugfs: File 'Analog Playback and Capture' in directory 'HDA Analog' already present! [ 532.954965] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 533.052406] sof-audio-pci :00:1f.3: firmware boot complete [ 543.902184] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 When I plug in a headset with a mic in the 3.5mm port, it still seems to use the internal mic instead of that of the headset. I also get a lot of popping sounds in the 3.5mm headset when playing audio, but that might not be related to this issue as I had that on kernel 5.3.0-41 as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868158] Re: Reopen issue 1666681
sorry but I'm not going to deal with bugs not respecting the code of conducts, also that bug is a duplicate as you knew when opening it, the fact that the issue has been wontfixed is not a reason to create extra work for others by registered a new ticket ** Changed in: nautilus (Ubuntu) Status: Confirmed => 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/1868158 Title: Reopen issue 181 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1865198 + kernel-stable-master-bug: 1867860 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Signoff phase-changed: Friday, 13. March 2020 17:28 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Stalled -- waiting for signoff variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1867860 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Signoff - phase-changed: Friday, 13. March 2020 17:28 UTC + phase: Holding before Promote to Updates + phase-changed: Thursday, 19. March 2020 22:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- stakeholder signoff not verified - stakeholder-signoff: Stalled -- waiting for signoff + promote-to-updates: Holding -- master bug not ready for release variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865197 Title: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868158] Re: Reopen issue 1666681
you also made your opinion clear on the other bug, the place to argue/contribute to that discussion is upstream, the Ubuntu team doesn't have the resources nor plan to invest engineering going against upstream choices there -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868158 Title: Reopen issue 181 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868179] [NEW] Typing in virtualbox during installation does not work
Public bug reported: I tried to install Ubuntu 19.10, 20.04 and 18.04.4LTS in virtualbox 6.1 on MacOS Catalina. The installating packages starts, the mouse works, so I can navigate all the way through to the user account creation screen. However, I cannot input anything using the keyboard. I can drag the dialogue text into the text fields but not delete/add by typing into the field. All keyboard input is ignored. I use the standards laptop keyboard of the mac which otherwise works fine. Since it fails in all versions specified above it is likely to be related to the combination of VirtualBox, MacOS and the ubuntu installe package. ** Affects: virtualbox Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid ** No longer affects: alsa-driver (Ubuntu) ** Package changed: ubiquity (Ubuntu) => virtualbox ** Also affects: ubiquity (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/1868179 Title: Typing in virtualbox during installation does not work To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1868179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865197 Title: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 186585] Fix included in openstack/tripleo-common 12.2.0
*** This bug is a duplicate of bug 147052 *** https://bugs.launchpad.net/bugs/147052 This issue was fixed in the openstack/tripleo-common 12.2.0 release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/186585 Title: emerald crashed with SIGSEGV in cairo_set_operator() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emerald/+bug/186585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1163155] Re: keep the 3 or 5 youngest linux-image-*-generic and autoremove the rest
We only keep a certain number of installed kernels, across all flavours. Older ones are autoremoved, even automatically with unattended-upgrades. ** Changed in: apt (Ubuntu) Status: New => Won't Fix ** Changed in: apt (Ubuntu) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1163155 Title: keep the 3 or 5 youngest linux-image-*-generic and autoremove the rest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1163155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866903] Re: Autopkgtest regression trigerred by Ruby 2.7
Version 0.20.1-2 already landed in unstable, ready to sync. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866903 Title: Autopkgtest regression trigerred by Ruby 2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-fakefs/+bug/1866903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677684] Re: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found
This issue still exists and should be fixed. I'm putting together with some other SRUs so all of them are done at once. Thanks @niedbalski for bringing up this issue. I'll fix Ubuntu Focal for now and try to get along with the needed SRUs. ** Changed in: corosync (Ubuntu Trusty) Assignee: Jorge Niedbalski (niedbalski) => (unassigned) ** Changed in: corosync (Ubuntu) Assignee: Jorge Niedbalski (niedbalski) => (unassigned) ** Changed in: corosync (Ubuntu Zesty) Assignee: Jorge Niedbalski (niedbalski) => (unassigned) ** Changed in: corosync (Ubuntu Xenial) Assignee: Jorge Niedbalski (niedbalski) => (unassigned) ** Changed in: corosync (Ubuntu) Importance: Medium => Undecided ** Changed in: corosync (Ubuntu Zesty) Importance: Medium => Undecided ** Changed in: corosync (Ubuntu Trusty) Importance: Medium => Undecided ** Changed in: corosync (Ubuntu Xenial) Importance: Medium => Undecided ** Also affects: corosync (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Also affects: corosync (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: corosync (Ubuntu Focal) Status: Incomplete => Confirmed ** Changed in: corosync (Ubuntu Eoan) Status: New => Confirmed ** Changed in: corosync (Ubuntu Disco) Status: New => Won't Fix ** Changed in: corosync (Ubuntu Bionic) Status: New => Confirmed ** Changed in: corosync (Ubuntu Zesty) Status: Incomplete => Won't Fix ** Changed in: corosync (Ubuntu Xenial) Status: Incomplete => Confirmed ** Changed in: corosync (Ubuntu Trusty) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1677684 Title: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb- blackbox: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1866932] Re: package snapd 2.44~pre1+20.04 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
Is this a duplicate of https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1865063? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866932 Title: package snapd 2.44~pre1+20.04 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1866932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867952] Re: package snapd 2.44+20.04 failed to install/upgrade: installed snapd package post-installation script subprocess was killed by signal (Terminated)
I wonder if this is related to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1865063? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867952 Title: package snapd 2.44+20.04 failed to install/upgrade: installed snapd package post-installation script subprocess was killed by signal (Terminated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1867952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677684] Re: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found
This issue still exists and should be fixed. I'm putting together with some other SRUs so all of them are done at once. Thanks @niedbalski for bringing up this issue. I'll fix Ubuntu Focal for now and try to get along with the needed SRUs. ** Changed in: corosync (Ubuntu Trusty) Assignee: Jorge Niedbalski (niedbalski) => (unassigned) ** Changed in: corosync (Ubuntu) Assignee: Jorge Niedbalski (niedbalski) => (unassigned) ** Changed in: corosync (Ubuntu Zesty) Assignee: Jorge Niedbalski (niedbalski) => (unassigned) ** Changed in: corosync (Ubuntu Xenial) Assignee: Jorge Niedbalski (niedbalski) => (unassigned) ** Changed in: corosync (Ubuntu) Importance: Medium => Undecided ** Changed in: corosync (Ubuntu Zesty) Importance: Medium => Undecided ** Changed in: corosync (Ubuntu Trusty) Importance: Medium => Undecided ** Changed in: corosync (Ubuntu Xenial) Importance: Medium => Undecided ** Also affects: corosync (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Also affects: corosync (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: corosync (Ubuntu Focal) Status: Incomplete => Confirmed ** Changed in: corosync (Ubuntu Eoan) Status: New => Confirmed ** Changed in: corosync (Ubuntu Disco) Status: New => Won't Fix ** Changed in: corosync (Ubuntu Bionic) Status: New => Confirmed ** Changed in: corosync (Ubuntu Zesty) Status: Incomplete => Won't Fix ** Changed in: corosync (Ubuntu Xenial) Status: Incomplete => Confirmed ** Changed in: corosync (Ubuntu Trusty) Status: Incomplete => 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/1677684 Title: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb- blackbox: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
(c)rafaeldtinoco@clusterdev:~/.../sources/ubuntu/corosync$ git diff HEAD diff --git a/debian/corosync-notifyd.init b/debian/corosync-notifyd.init index c908618..837e48a 100644 --- a/debian/corosync-notifyd.init +++ b/debian/corosync-notifyd.init @@ -21,7 +21,6 @@ NAME=corosync-notifyd DAEMON=/usr/sbin/$NAME PIDFILE=/var/run/$NAME.pid SCRIPTNAME=/etc/init.d/$NAME -PIDFILE=/var/run/corosync.pid RARUNDIR=/var/run/resource-agents # Exit if the package is not installed If anyone faces this issue, just remove the second PIDFILE as it appears to be a leftover. I'll fix this and point this out to Debian as it also faces the same issue. NEVERTHELESS, remember that this issue would only exist if you are using the "sysv" scripts OR the sysv-generator (making systemd to control the service through sysv scripts). All others are probably relying in systemd to start/stop/monitor corosync daemon (/lib/systemd/system/corosync.service). -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1437359 Title: A PIDFILE is double-defined for the corosync-notifyd init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
