It looks like installation of this update may have resolved the issue on
our systems:
ethtool/jammy-updates 1:5.16-1ubuntu0.1
I believe that release was put together as a result of this bug report,
which may or may not be a duplicate:
I just went back to another machine that doesn't have "ethtool/jammy-
updates 1:5.16-1ubuntu0.1" installed yet. It also produces correct
output when I run "sudo ethtool --module-info eno3" now.
I think it's likely that this issue was fixed by some previous release
and I just didn't notice it
This should not impact Ubuntu Cinnamon as I don't believe there are any
components that specifically rely heavily on gnome-software.
ubuntucinnamon-meta will need to add the new entry for gnome-software-
plugin-deb, but that's about it.
--
You received this bug notification because you are a
** Changed in: mozjs102 (Ubuntu)
Assignee: (unassigned) => Joshua Peisach (itzswirlz)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058787
Title:
proposed-migration for mozjs102 102.15.
** Also affects: ubuntucinnamon-wallpapers (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntucinnamon-environment (Ubuntu)
Assignee: (unassigned) => Joshua Peisach (itzswirlz)
** Changed in: ubuntucinnamon-wallpapers (Ubuntu)
Assignee: (unassigned) =>
Addressing the challenge of non-deterministic SIM selection for mobile
data in your Ubuntu-based system, especially when managing calls and SMS
with ofono for your home automation and alarm system, necessitates a
multifaceted approach. Firstly, ensuring that your ofono installation
and the WIKO
This is still a thing. As mentioned here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901931#58 you just need to
remove timidity from the audio group -- go to your /etc/group file and find the
line
audio:
and remove timidity. Save & restart.
--
You received this bug notification
Public bug reported:
Hello! When trying to bootstrap a new arm64 rootfs using the upcoming
Noble release the systemd post-installation script will fail. Please see
the file debootstrap.log attached for package install logs.
To reproduce:
$ sudo debootstrap --no-merged-usr --arch arm64 noble
: rust-regex
UpgradeStatus: No upgrade log present (probably fresh install)
** Changed in: rust-regex (Ubuntu)
Assignee: (unassigned) => Joshua Peisach (itzswirlz)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Patch added: "Proposed Jammy Patch"
https://bugs.launchpad.net/ubuntu/+source/rust-regex/+bug/1977694/+attachment/5594991/+files/rust-regex_1.5.4-1ubuntu0.1.debdiff
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are
This even happened to me on Focal (latest update) when reporting the
gthumb CVE I found. I manually uploaded the crash dump, separated the
big apport file and put it up. Maybe a server issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hey Amir, can you still reproduce this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803078
Title:
Screensaver unlock screen shown twice after playing video
To manage notifications about this
** Description changed:
[For some reason, the autoreporter wasn't opening Launchpad so I'm
bugging this manually]
CVE-2019-20326 - if gThumb tries to load an image greater than Cairo's
max drawing size, it will crash. This is a heap-based buffer overflow an
attacker could execute
** Description changed:
[For some reason, the autoreporter wasn't opening Launchpad so I'm
bugging this manually]
CVE-2019-20326 - if gThumb tries to load an image greater than Cairo's
max drawing size, it will crash. This is a heap-based buffer overflow an
attacker could execute
focal patch
** Patch added: "gthumb_3.8.0-2.1ubuntu0.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1976189/+attachment/5593642/+files/gthumb_3.8.0-2.1ubuntu0.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3567
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912060
Title:
[SRU] caribou: Segfault (as regression of xorg CVE-2020-25712
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-20326
** Tags added: focal-security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976189
Title:
[CVE-2019-20326] gthumb crashes
ed in: gthumb (Ubuntu)
Assignee: (unassigned) => Joshua Peisach (itzswirlz)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976189
Title:
[CVE-2019-20326] gthumb crashes when trying
I don't have a syslog or a backtrace so I can't do anything about it,
but if any of the images were above the 32k integer limit, it would be
CVE-2019-20326.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-20326
--
You received this bug notification because you are a member of
I was able to open nautilus after turning WiFi off. Atom also was then
able to open the project folder.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951075
Title:
Nautilus doesn't load and gives
I get this error when Atom crashes.
Just a bunch of "this is deprecated"
"
/usr/bin/atom: line 195: 16065 Killed nohup "$ATOM_PATH"
--executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
(node:16144) Electron: Loading non-context-aware native module in renderer:
I have exactly the same issue but keybase is not installed on my system.
I am running stock Ubuntu 22.04 .
This issue happened after I did apt dist-upgrade a couple of days ago (May
4th?).
I upgraded my system to 22.04 from 21.10 when 22.04 was publicly released.
I used the software-updater to do
This is discussed here: https://github.com/pypa/pipenv/issues/5088
This error occurs with the system package:
```
vagrant@vagrant:~$ which pipenv
/usr/bin/pipenv
vagrant@vagrant:~mojo_coordinator$ dpkg -S /usr/bin/pipenv
pipenv: /usr/bin/pipenv
vagrant@vagrant:~$ dpkg -l pipenv
** Description changed:
I was looking at this code and it looks like it just loops through each
disk found and then runs the wipe.
https://github.com/maas/maas/blob/master/src/metadataserver/user_data/templates/snippets/maas_wipe.py
When you have a machine with 25 SSDs that don't
Would it be possible to parallelize this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968453
Title:
Parallelize maas-wipe
To manage notifications about this bug go to:
Public bug reported:
I was looking at this code and it looks like it just loops through each
disk found and then runs the wipe.
https://github.com/maas/maas/blob/master/src/metadataserver/user_data/templates/snippets/maas_wipe.py
When you have a machine with 25 SSDs that don't support secure
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968382
Title:
gnome-control-center crashed with SIGSEGV
To manage notifications about this bug go
Confirmed on Ubuntu Cinnamon Remix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964923
Title:
list-oem-metapackages crashed with AttributeError in
packages_for_modalias(): 'Cache' object has no
Reproduced on Cinnamon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962585
Title:
tracker-extract-3 crashed with signal 31 in __GI___ioctl()
To manage notifications about this bug go to:
I need to update this issue. Version 2.4.8 of thermald does NOT fix
this issue. This is not a hardware issue per se because under Windows,
this throttling does not occur. (Under Windows, the machine is able to
run a bit hotter and without throttling.) I speculate that Dell has
written drivers
Public bug reported:
Reproduced on Ubuntu Cinnamon 22.04
Open cinnamon-settings -> Network section -> causes this crash. May be a
cinnamon-settings issue.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: python3.9-minimal 3.9.10-1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
*** This bug is a duplicate of bug 1958412 ***
https://bugs.launchpad.net/bugs/1958412
+1, I have the same issue as here, and not #1958412 (grub workaround
described there doesn't fix the issue). Though maybe it is marked as
duplicate if the underlying issue is the same in both cases...
--
Public bug reported:
There have been many reports of improper CPU throttling on Intel CPUs to
the point of making machines completely unusable. See for example:
https://www.dell.com/community/Latitude/Latitude-5420-7420-7520-CPU-
Throttling-Issue-on-
Public bug reported:
Hello, I see that the Dell Latitude 5420 is Ubuntu 20.04 Certified. But
there seems to be a major issue that is known about the cpu throttling
down to 400MHz under pretty much any heavy workload. I've contacted dell
support about this issue and they have been less then
Unfortunately, and I have found another bug about similar issues with
patches, on Ubuntu Jammy 22.04 server (preinstalled), I am getting the
same issue on my raspi (arm64).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Ubuntu Jammy Core - Smoke test fails.
One of the issues that I believe may be the primary issue is that apt-
key has no access to /dev/null.
root@Joshua-PC:/# apt-get update
Ign:1 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:2 http://security.ubuntu.com
** Attachment added: "partman.txt"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1955719/+attachment/5549501/+files/partman.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955719
Public bug reported:
Jammy 22.04 testing - Kubuntu was already installed. I auto-resized to
install Ubuntu MATE alongside it, and rebooting no boot option, or GRUB
option to boot to Kubuntu existed. I even tried sudo update-grub but
stil nothing.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Public bug reported:
Testing Ubuntu Jammy Daily iso for 12/23/2021. Whole memtest is failing
(PIIX3 chipset, EFI disabled, I/O APIC on)
CPU: AMD Ryzen 5 3600
RAM: ~10G
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: memtest86+ 5.01-3.1ubuntu5
ProcVersionSignature: Ubuntu
Testing again today, and the patch does continue to work. I can no
longer reproduce the bug following the same steps as earlier, and I
cannot find any regression as a result.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification
Hello, I've been busy with school and life - Cinnamon 5.2 is currently
WIP in Debian experimental
This shouldn't slow anything down significantly. The only slowing that
could happen is processing and checking the issue on info change.
I can agree that this may not be as important but it
So the patch works in Focal - same process except there is no button
cobbling at the top. But what does the autopkgtest regression mean now
that it is gone? It seems to not have caused an issue-this shouldn't
have caused any in the first place. Now all the autopkgtests has passed.
Now what?
--
Solutions-qa testing is finished. +1 from us!
Bionic Test Plan:
https://solutions.qa.canonical.com/testplans/testplaninstance/8d0c033e-3b40-4ef9-b68d-0451064e4256
Focal Test Plan:
https://solutions.qa.canonical.com/testplans/testplaninstance/d9c33bd2-6083-4937-9ef0-7fdff2852617
--
You received
I'm not that interested in groovy/hirsute, but feel free to play with it
if you *really* wish.
** Patch added: "cinnamon_4.8.6-2ubuntu0.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1919026/+attachment/5533324/+files/cinnamon_4.8.6-2ubuntu0.1.debdiff
--
You received
** Description changed:
- In the user creation dialog if you create a user that already exists (or
- try to), a GLib.Error is thrown and the dialog holds. I will make a
- patch for this.
+ [Impact]
+
+ * In the user creation dialog if you create a user that already exists
+ (or try to), a
** Description changed:
In the user creation dialog if you create a user that already exists (or
try to), a GLib.Error is thrown and the dialog holds. I will make a
patch for this.
Affected:
Focal - Cinnamon 4.4.8
- Groovy - Cinnamon 4.6.7
- Hirsute - current unstable. Check Debian
Public bug reported:
Using Ubuntu 21.04 on bare metal. When attempting to perform a scan of
an entire subnet, I receive the following error:
sudo nmap -sn 192.168.0.1/24
Starting Nmap 7.80 ( https://nmap.org ) at 2021-10-14 10:14 EDT
nmap: Target.cc:503: void Target::stopTimeOutClock(const
We have an ubuntu server running a set of eight Samsung 980 Pro PCIe 4.0
NVMe SSDs (model MZ-V8P1T0BW) on Ubuntu 20.04.3 LTS (GNU/Linux
5.4.0-88-generic x86_64). We've seen this happen at least 5 times over
the past month, and not always on the same SSD. We first saw it happen
on 5.4.0-81. Some
Public bug reported:
My touchpad is completely failing me. Help me please.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2
ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1939223/+attachment/5516685/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
See apport info above. Note that I have already modified the
aforementioned iptables_init.sh and iptables_removeall.sh scripts to
work around this bug, and this is why apport will show these files as
modified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Tags added: apport-collected focal
** Description changed:
Package info:
Package: miniupnpd
Version: 2.1-6.1
Priority: optional
Section: universe/net
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Thomas Goirand
My system info:
Public bug reported:
Package info:
Package: miniupnpd
Version: 2.1-6.1
Priority: optional
Section: universe/net
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Thomas Goirand
My system info:
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
** Description changed:
- Google Instances deployed with the Ubuntu 12.10 Daily images are
+ Google Instances deployed with the Ubuntu 21.10 Daily images are
inaccessible via SSH.
gcloud compute instances create sf-impish-v20200720 --zone us-west1-a
--network "default"
Verification steps:
1. Enabled Confidential Compute
2. Change image to daily-ubuntu-2104-hirsute-v20210510 (last working image)
3. Launched image
4. Enabled proposed
5. Updated system https://paste.ubuntu.com/p/mNrZNkVYtB/
6. Rebooted sucessfully! https://paste.ubuntu.com/p/G9CmvhW9tx/
Marking
# GCE Verification
## Test Steps
Booted GCE amd64 systems with uEFI-only and uEFI+Secure Boot
Ran the following script: https://paste.ubuntu.com/p/K2DpvcbYNG/
Ensure system successfully reboots
## Xenial Results
uEFI only: https://paste.ubuntu.com/p/nwcjCSVTRD/
uEFI+Secure Boot:
# Steps to reproduce
1. $ multipass launch bionic --name b1
2. $ multipass exec b1 bash
3. $ sudo apt update
4. $ sudo apt install aide
5. At the MTA configuration select "No configuration"
6. $ sudo run-parts /etc/cron.daily
7. $ sudo run-parts /etc/cron.daily
8. $ sudo ls /run/aide
At this
Fixed patch in version
** Patch removed: "nemo_4.4.2-2ubuntu1.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nemo/+bug/1935849/+attachment/5510611/+files/nemo_4.4.2-2ubuntu1.1.debdiff
** Patch added: "nemo_4.4.2-2ubuntu2.debdiff"
** Summary changed:
- Reenabling toolbar in two-pane view causes the toolbar on each pane to think
its two separate nemo main toolbars
+ [SRU] Reenabling toolbar in two-pane view causes the toolbar on each pane to
think its two separate nemo main toolbars
** Changed in: nemo (Ubuntu)
Patch available
** Description changed:
Ubuntu Cinnamon Remix 20.04.2:
- When enabling two-pane view (F3, or View -> Extra Pane), and going to
- View and disabling then reenabling the toolbar, all the information that
- was only on one side of the toolbar is now on both sides. This leads to
** Description changed:
Ubuntu Cinnamon Remix 20.04.2:
When enabling two-pane view (F3, or View -> Extra Pane), and going to
View and disabling then reenabling the toolbar, all the information that
was only on one side of the toolbar is now on both sides. This leads to
some weird
Package: nemo
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: nemo (Ubuntu)
Importance: Undecided
Assignee: Joshua Peisach (itzswirlz)
Status: New
** Tags: amd64 apport-bug focal
** Attachment added: "Congested toolbar"
https://bugs.lau
Why is this closed? This is still an unresolved issue; my Lenovo X220
with a Centrino Wireless-N 1000 has never worked properly on Ubuntu
18.04 OR 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
5.11.0-22-generic can no longer compile kvdo from source, failing with:
```
Skipping BTF generation for /src/kvdo/vdo/kvdo.ko due to unavailability of
vmlinux
make: Leaving directory '/usr/src/linux-headers-5.11.0-22-generic'
```
Even though ddebs + dbgsym are installed. :(
An Ubuntu package /
# GCE Verification
## Test Steps
Booted GCE amd64 systems with uEFI-only and uEFI+Secure Boot
Ran the following script: https://paste.ubuntu.com/p/K2DpvcbYNG/
Ensure system successfully reboots
## Xenial Results
uEFI only: https://paste.ubuntu.com/p/kqjn5YbYCb/
uEFI+Secure Boot:
Public bug reported:
After gpg v2.1, the --pinentry-mode=loopback flag is required to use the
--passphrase, --passphrase-fd, and --passphrase-file flags with gpg.
`--pinentry-mode=loopback` will need to be added to the command line
arguments for gpg during signing for the case where a passphrase
I don't feel safe downgrading the package as
https://serverfault.com/a/993629/272284 warns that this could break the
system and my general ignorance on the subject.
Will this resolve by itself once the new version superseding
2.31-0ubuntu9.3 is released and I update or are updates jammed as the
# Xenial AWS Verification
## Test Steps
Booted AWS arm64 baremetal and VM systems
Ran the following script: https://paste.ubuntu.com/p/B5XPR8StXy/
Ensure system successfully reboots
## Results
t4g.medium: https://paste.ubuntu.com/p/ys4hgfTfRm/
c6g.metal: https://paste.ubuntu.com/p/2RFYbCmFxh/
Marking verification done
** Tags removed: verification-needed verification-needed-bionic
verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
# Bionic Verification
## Test Steps
Booted AWS arm64 baremetal and VM systems
Ran the following script: https://paste.ubuntu.com/p/B5XPR8StXy/
Ensure system successfully reboots
## Results
t4g.medium: https://paste.ubuntu.com/p/QH8Xrr4Sck/
c6g.metal: https://paste.ubuntu.com/p/4q688QqC4v/
After verifying that the "error" messages in #15 is ignorable, marking
this verification done.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-xenial
--
You received this bug
Testing complete, if someone can explain the error messages in comment
#15 we can mark this verification-done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930742
Title:
cloud images in xenial do
# GCE Verification
## Test Steps
Booted GCE amd64 systems with uEFI-only and uEFI+Secure Boot
Ran the following script: https://paste.ubuntu.com/p/BDwhF4KHZ2/
Ensure system successfully reboots
## Xenial Results
uEFI only: https://paste.ubuntu.com/p/vhxkYy5F43/
uEFI+Secure Boot:
# Bionic AWS Verification
## Test Steps
Booted AWS arm64 baremetal and VM systems
Ran the following script: https://paste.ubuntu.com/p/B5XPR8StXy/
Ensure system successfully reboots
## Results
t4g.medium: https://paste.ubuntu.com/p/QH8Xrr4Sck/
c6g.metal: https://paste.ubuntu.com/p/4q688QqC4v/
# Xenial AWS Verification
## Test Steps
Booted AWS arm64 baremetal and VM systems
Ran the following script: https://paste.ubuntu.com/p/B5XPR8StXy/
Ensure system successfully reboots
## Results
Both systems successfully updated grub from proposed and rebooted
t4g.medium:
Public bug reported:
# Overview
Hirsute and Impish daily builds are currently not booting on Google
Confidential Compute. Confidential compute is Google's platform that
enables the use of Secure Encrypted Virtualization extension via AMD
EPYC CPUs. Booting an image with version 1.45 works, but
Launched c6g.metal, a1.metal, and t4g.medium instance with Xenial
(20210429) on upgrade of all three I got the following error:
grub-install: error: relocation 0x113 is not implemented yet.
Failed: grub-install --target=arm64-efi
WARNING: Bootloader is not properly installed, system may not be
Public bug reported:
I dual booted my laptop lenovo slim 3 and with the dual boot, my
touchpad is not working
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux
Google has confirmed that the SRU has successfully passed their tests
and previously failing tests are now consistently passing. Marking fixed
verified.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-groovy
Test images were delivered to Google with images with the following
versions:
* bionic-livecd.ubuntu-cpc.gce.devel.manifest
google-compute-engine-oslogin20210429.00-0ubuntu1~18.04.0
* focal-livecd.ubuntu-cpc.gce.devel.manifest
google-compute-engine-oslogin
Marking verification-done for all releases.
Images were successfully generated with the following versions of
google-guest-agent from proposed:
bionic: 20210414.00-0ubuntu1~18.04.0
focal: 20210414.00-0ubuntu1~20.04.0
groovy: 20210414.00-0ubuntu1~20.10.0
hirsute: 20210414.00-0ubuntu1
These
And focal verification done, same process/results
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912060
Title:
[SRU] caribou: Segfault (as
All done - Groovy patch does work.
How to reproduce bug pre-patch:
1) Lock screen
2) Navigate to advanced characters in virtual keyboard
3) Press the euro sign and cinnamon-screensaver crashes. In the screenshot I
post you can see the clear Xorg error it posts.
After patch, no issues what so
I have not. I'm bad
I just tested and I found even using the normal characters using the
virtual keyboard like the euro sign crashes the screensaver. Yikes!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cinnamon-settings-daemon (Ubuntu)
Assignee: (unassigned) => Joshua Peisach (itzswirlz)
** Changed in: cinnamon-settings-daemon (Ubuntu)
Status: New => Confirmed
** Description changed:
when I try to open csd-wacom it just crashes. On terminal I c
Per the diff there are two merge issues
https://launchpadlibrarian.net/536068009/u-boot-
menu_4.0.2ubuntu5_4.0.3ubuntu1.diff.gz
fwiw this is blocking impish builds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Groovy patch. The patch file is the same, this is just really an
adjusted changelog and patch file name.
** Patch added: "cinnamon_4.6.7-1ubuntu1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1919026/+attachment/5494404/+files/cinnamon_4.6.7-1ubuntu1.2.debdiff
--
You
I found out what the issue was. The problem is the new linux kernal
update Linux 5.8.0-50-generic.
After booting up with Linux 5.8.0-48-generic (the previous one), the
problem is resolved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have a debdiff/patch for this, based on two commits-one is the actual
patch and another one is a localization fix. I put them into one if
whoever reviews doesn't mind.
** Patch added: "cinnamon_4.4.8-4ubuntu0.3.debdiff"
Public bug reported:
Ubuntu was perfect before updating it.
I ran the command sudo apt update. After that, my computer graphics have
become choppy. I have attached a screenshot of the problem.
Description:Ubuntu 20.04.2 LTS
Release:20.04
00:02.0 VGA compatible controller: Intel
Marking confirmed
# Steps to reproduce
1. wget
http://cloud-images.ubuntu.com/daily/server/buildd/daily/xenial/current/xenial-server-cloudimg-amd64-disk.img
2. Modify /etc/boot/grub.cfg to add "console=ttyS0" to kernel command line
3. Boot using the following qemu CLI:
qemu-system-x86_64 \
# Upgrading Xenial to Bionic on GCE
Running again with the correct, newer release-upgrader version from
today
1. Launched GCE instance
2. Installed google-cloud-sdk snap
3. Updated system
4. Verified the tracking channel was updated
$ sudo snap install google-cloud-sdk --channel
# Upgrading Xenial to Bionic on GCE (again with more logs this time)
1. Launched GCE instance
2. Installed google-cloud-sdk snap
3. Updated system
4. Verified the tracking channel was updated
$ sudo snap install google-cloud-sdk --channel latest/stable/ubuntu-16.04
--classic
# update /etc/update-manager/release-upgrades to Prompt=normal
$ sudo snap info google-cloud-sdk
name: google-cloud-sdk
summary: Google Cloud SDK
publisher: Cloud SDK (google-cloud-sdk✓)
store-url: https://snapcraft.io/google-cloud-sdk
license: unset
description: |
Command-line
# Upgrading Xenial to Bionic on GCE
1. Launched GCE instance
2. Installed google-cloud-sdk snap
3. Updated system
4. Verified the tracking channel was updated
name: google-cloud-sdk
summary: Command-line interface for Google Cloud Platform products and
services
publisher: Cloud SDK
# Upgrading Xenial to Bionic on GCE (again with more logs this time)
1. Launched GCE instance
2. Installed google-cloud-sdk snap
3. Updated system
4. Verified the tracking channel was updated
$ sudo snap install google-cloud-sdk --channel latest/stable/ubuntu-16.04
--classic
# Upgrading Bionic to Focal on GCE
1. Launched GCE instance
2. Installed google-cloud-sdk snap
3. Updated system
4. Verified the tracking channel was updated
$ sudo snap info google-cloud-sdk
name: google-cloud-sdk
summary: Google Cloud SDK
publisher: Cloud SDK (google-cloud-sdk✓)
Marking affects linux, so the kernel folks can weigh in on this.
** Also affects: linux (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/1925008
Investigating your other bug caused me to find:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-
rootfs/+merge/398027
Which will set up a custom grub config without quiet. Looking at a
hirsute image, this appears to be the case already. What is remaining is
the SRU back to
Adding livecd-rootfs as this is where I believe this would be changed.
In livecd-rootfs, CPC images get a 50-cloudimg-settings.cfg where
GRUB_CMDLINE_LINUX_DEFAULT is set without quiet. Similarly, ubuntu-core
does something similar in their hooks.
--
You received this bug notification because
1 - 100 of 7799 matches
Mail list logo
