Public bug reported:
Mysql noch nicht konfiguriert.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: icinga2-ido-mysql 2.11.2-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon
** Description changed:
Hello everyone,
I'm a KDE neon user and noticed that on my installation, the required
- hard disc space keeps increases after each kernel updates. The reason is
+ hard disc space keeps increases after each kernel update. The reason is
that after installing a new ke
Hints added to linux-kvm, so it should pass the ADT tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922800
Title:
Nvidia proprietary DKMS drivers cannot build in linux-kvm 5.8 and
subsequent
ignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Affects: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux-kvm (Ubuntu Groovy)
Importance: Undecided
Assignee: Guilherme G. Piccoli (gpiccoli)
Statu
The ADT test was hinted on linux-kvm, since it's related with a kernel
config that is disabled, this is what we should do.
Also, regarding the test has never been executed, this is explained in
LP: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1915051
Cheers,
Guilherme
** Changed in: li
ctstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/v/virtualbox-
hwe/20210225_192413_d067f@/log.gz
** Affects: linux-kvm (Ubuntu)
Importance: Undecided
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
--
You rece
Another oddity: for some reason, installing virtualbox-guest-dkms-hwe
forces the kernel packages removal - I'm not sure why.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922397
Title:
ADT test fai
** Attachment added: "linux-kvm-1034.vbox"
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1922397/+attachment/5483639/+files/linux-kvm-1034.vbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Attachment added: "linux-kvm-1037.vbox"
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1922397/+attachment/5483640/+files/linux-kvm-1037.vbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Hi Jitendra, thanks for the effort! Let me know your issues with kdump, hope I
can help.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914456
Title:
120 sec kernel timeout is se
hi Bambang, the fix is present in the current proposed version, 4.15.0-141 -
both versions 4.15.0-139 and -140 are CVE fixes only, so they didn't include
the KVM fix.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
sorry, I had an old binary in /usr/local
** Changed in: gtk-gnutella (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/1921846
Title:
won't start, need libgtk-1.2
Public bug reported:
when starting it from the command line, it reports
gtk-gnutella: error while loading shared libraries: libgtk-1.2.so.0:
cannot open shared object file: No such file or directory
so there is a missing dependency in the package control file
a.
ProblemType: Bug
DistroRelease
Hi Jitendra, I am sorry for the delay - I've tried to reproduce both using
regular SCSI device in a virtual machine and by using iSCSI, and neither was a
successful reproducer. Based on the stack traces I see in your "echo w" output,
it seems to be related with your special iSCSI target.
Also, w
Thanks kailoran, indeed it was added after 5.6 - my goal was the test on 5.10,
I should have been more clear about that heheh
Cheers!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919425
Title:
Sy
Thanks for the report! This seems to be fixed by [0], and this patch is
available in Azure kernel 5.4.0-1041 - can you try it? The fixed kernel
is available in -updates / -security pockets.
Thanks,
Guilherme
[0] git.kernel.org/linus/2f941622fd88
--
You received this bug notification because
Thanks for the report! Can you both boot the machine fresh and enable
oops_backtrace, by executing "echo 1 | sudo tee
/proc/sys/kernel/oops_all_cpu_backtrace" ? Then I'll need the full
dmesg, after the issue happens, as kailoran updated.
If that is not enough we might need a kdump later.
Thanks in
Hi Jitendra, my sincere apologies for the delay, I'm still trying to reproduce
this.
I hope to have more meaningful updates for you until the end of this week.
Meanwhile, let me ask you something: would you be wiling to collect a
kdump if the issue reproduces again? That'd be a helpful tool to
in
** Changed in: linux-azure (Ubuntu Groovy)
Status: Fix Committed => 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/1914830
Title:
Mellanox Patches To Prevent Kernel Hang In MLX4
Oh, so as per Greg KH comment [0] this is not a problem in the kernel itself,
but in out-of-tree modules relying on a specific behavior; he even rejected a
"fix" patch [1].
That said, I agree on marking this one as invalid!
Thanks again for the great finding Hassan!
[0] https://lists.openwall.n
Thank you Hassan for nailing it down. But does it mean Ubuntu 5.8.0-45 suffers
from this, right? It is something to aware and merge a fix if any is/will be
available.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, so how about if you install the kernel version 5.8.0-43 in your
system? In order to do that, I suggest you to boot using the Live CD and
use chroot - there are goos instructions here :
https://askubuntu.com/a/28100
The only thing to change is step 6: please run "sudo apt-get install
linux-ima
Thanks for the report Hassan! Can you please add "ignore_loglevel" to
you GRUB configuration, run "sudo update-grub" and try to boot with
5.8.0-45? We'll need to get some information from kernel log to
understand what's possibly going wrong.
Thanks,
Guilherme
--
You received this bug notificat
Hi Sam, thanks for the report. Is there any activity that you can do in
order to trigger the crashes, or are them of nowhere? Also, what do you
consider a crash - the machine reboots? Can you see something in the
screen?
I'd like to see a kernel log when that crash happens - one alternative is to
Could narrow the problem down to both a Grub issue, but more relevant -
to a Dell BIOS issue as well. So, 2 bugs!
Regarding GRUB, the disk information is read through the int 13h/service
48h from BIOS[0]. But testing in an HP machine (with HW RAID as well),
and comparing that with what we call the
After checking the fibmap files from the user, could verify that the
LBAs for the non-working files are very large compared to the ones that
are working - it's a data point reinforcing the theory that GRUB is
miscalculating something for files after some LBA offset.
Managed to reproduced the issue
Same on Kubuntu 20.10 and Lenovo Legion 5 / AMD / nvidia + uefi +
"secure boot support"=enabled. The system was installed in this config.
The issue was resolved by/after the following actions:
- setting admin password in uefi
- disabling "secure boot support"
The problem remains resolved after en
oot/vmlinuz-4.4.0-194-generic > hdparm-vmlinuz194-b.out
debugfs -R "stat /vmlinuz-4.4.0-194-generic" /dev/sda2 >
debugfs-vmlinuz194-r.out
hdparm --fibmap /vmlinuz-4.4.0-194-generic > hdparm-vmlinuz194-r.out
[0] https://askubuntu.com/q/867047
[1] https://askubuntu.com/
OK, I understand..the request then is for cancelling the integrity test
*once it has started*. Can you open a new bug, with a very clear/direct
title about this? Something like "Add a way to cancel integrity test on
Ubuntu server ISO once it has started", so we can track this feature
request over t
I am a happy user of the Ubuntu systems "account online" service happy, so
far I think .. or maybe not now?!?
it makes me think that between now and March 15 we could all be left on foot
... but what is Google? Did she start strangling her babies one after another?
--
You received this bug
Thanks for the clarification Jitendra, and for correcting my command! It
was indeed wrong, apologies - the correct file to write is the one
you've used, "/proc/sysrq-trigger".
So, it seems we have a lock "situation" in iSCSI/scsi, I'll need to study more
the code to understand how that is trigger
Sorry Ulrich, I got a bit confused. What is not true?
This Launchpad bug is about users being unable to *skip* the integrity
check. After the test from Camille and I (and you!), seems this is
indeed fixed, users *can* skip the integrity check if they want,
correct?
We are not discussing here if t
What is the output of "ubuntu-drivers devices" in your system?
As I mentioned to you, there are multiple nvidia drivers, like -340, -440, -460
... you might have support for your card in a new version, which would be
better than using an old version.
--
You received this bug notification becaus
So, when the system is working fine, before the freeze, can you SSH into
it?
Also, what is the kernel version running in the Live image you're booting
there? This information shows early in the kernel logs...but you can also
collect using the "uname -a" command. I'd like to compare the version o
Awesome, I'm glad that you nailed the issue. Guess using the nvidia driver is
an option then, right?
Cheers!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917265
Title:
Suspending to RAM freezes c
Thanks a lot for the tests Bambang, and for the report! The patch was submitted
to the Ubuntu kernel ML, soon it should be applied.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
: The dosemu freezes on loading
I have also reported this problem to dosemu2 developer, here is my bug report:
https://github.com/dosemu2/dosemu2/issues/1404
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Gui
Well, seems it's fixed for Focal/Groovy - so I marked as Fix Released.
Let us know if any issues are observed Camille and Sebastian.
Thanks,
Guilherme
** Changed in: casper (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: subiquity
Status: New => Fix Released
--
You re
Hi Ariel, thanks for the pictures! This is interesting, seems you're
facing a USB host controller breakage, so all your USB devices are
frozen. Can you try something, in order for us to be sure about that?
Please, setup a SSH server [0], and after the freeze, try to connect to
the machine using SSH
Unfortunately there is nothing relevant on logs in a first sight; your
theory is interesting, is it possible for you to give a try to Nvidia
drivers? At least as a data point.
You could try "ubuntu-drivers devices" to show the latest nvidia driver
supported by your device, and use it for a while,
Hi Bambang, thanks a lot for your testing! I'll need you to test one
more kernel to be 100% sure of the issue and be able to fix it. Let me
elaborate on what's happening.
So, since kernel 4.15.0-136 we included a very complex KVM fix for a
kind of "race" in interrupt window triggered by David Wood
So Bambang and/or Hans-Christian, can you please test the following
kernel build that includes the aforementioned missing commit:
https://kernel.ubuntu.com/~gpiccoli/lp1917138-2/
It's the same process as before, just install all the packages from the link
above, reboot and retry the reproducer -
Thanks Bambang, let me know as soon as possible, so we can maybe fix
this cycle (worst case, next cycle).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917138
Title:
kernel 4.15.0-136 causes dosemu
OK, please attach /var/log/{kern.log,syslog} so we can take a look, we
may need to run some experiments. Also, do you have a working version?
Like "in version X it *always* works, starting in kernel version Y, it's
flaky".
Cheers,
Guilherme
--
You received this bug notification because you are
Thanks again Bambang and Hans-Christian for the report, it seems indeed
a bug in the kernel. I think I know what's going on, but I'd like to ask
you to perform some testing in order we can prove that, and then fix it.
So, first it'll be 2 tests - depending on the result, a third test will be
nece
Thanks for the report! Are you using nested virtualization (a virtual machine
inside another virtual machine) or you run dosbox directly in your
host/bare-metal system?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Changed in: linux-azure (Ubuntu Groovy)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu Groovy)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
An user who reported the issue confirmed the kernel with the patches hereby
proposed is not reproducing anymore; also, I checked in the Bionic git tree,
patches are indeed there.
Cheers,
Guilherme
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You rece
Hi Ariel, thanks for your report! So, let me clarify: now your system is
freezing on boot, you don't need to run "lspci" to observe the freeze anymore?
Can you try adding "ignore_loglevel" in the kernel command-line on Grub, and
observe the boot progressing? If so, then please take a screenshot/
Can you also attach the syslog? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917265
Title:
Suspending to RAM freezes computer
To manage notifications about this bug go to:
https://bugs.la
Thanks Jarno. Can you run a test with them? Force one method to be used (like
"deep"), following the commnad-line option in LP #1885085, and run 10 tests...5
of them after a reboot.
After that, force the other and re-run the tests. Let's see if we can narrow
your issue to one suspend method.
Th
Hi Jarno, can you please confirm if that behavior you observed is not
explained by
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885085 ?
Thnaks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
The last patch stores the state of the "More" expanders and should
remember the window size (might not work for some reason).
I suggest to create new tickets if something needs fine-tuning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Hi Jitendra, thanks for the data you provided. I have some questions in
order I can better simulate your environment:
(a) You said "vendor's iSCSI target" <- can you elaborate more about
this, like which vendor/solution are we talking about?
(b) You mention, in the last comment: "note that Ubuntu
Well...we can discuss that in a different LP heheh
I'm sure lots of people will love that idea, and a bunch of people will hate it.
I'll try to find some LP in which the discussion fits better - if I
can't find, I'll open one and add you there! Thanks,
Guilherme
--
You received this bug notifi
Cool, I'm glad that it's being considered! I'd go with "ttyS0" - if it's
not right, patience...won't work. But there's no downside in that case,
it'll behave as it currently behaves, no output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Attachment added: "groovy.png"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1892369/+attachment/5466722/+files/groovy.png
** No longer affects: ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Sebastian / Camille, I've just tested in a virtual machine, and the
parameter "fsck.mode=skip" worked for me in both cases (Groovy and Focal
20.04.2 images); I'll attach screenshots with the results (I needed to
use a VNC connection since by default the images don't output to serial
console, anothe
Hi Jitendra, thanks for the heads-up. Can you collect the output of the
following commands, in the machines's current state ? (no need to
reproduce for that)
"dmesg", "lspci -vvv", "lsblk", "ls -l /sys/block", "mount"
That'd help a lot to determine what is your hardware and maybe help me to
repr
** Changed in: linux-azure (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: linux-azure (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** 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/1916076
Title:
Support kernel 4.15 in Trusty kexec-tools
To manage notifications about this bug go t
Oh, I am sorry to hear that. I wish you luck in fixing the HW problem, and when
that happens, let us know and we can continue this debug if possible.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Hi Jitendra, thanks for your prompt response. I'd like to ask you the
following data in order to speed-up the debug process:
1) Right before the test, please collect the outputs of: "dmesg", "lspci
-vvv", "lsblk", "ls -l /sys/block", "mount"
2) After the I/O test + SCSI removal, collect please a
Hi Jitendra, thanks for your report! Could you collect a sosreport for us, in
order we can have more information (even to try reproducing the issue in-house)?
For that, please execute the following commands as root user:
apt-get install sosreport
sosreport
A "sosreport-X.tar.xz" file will be
Thanks a lot for your testing ! Do you mind in testing Groovy ISO [0] as well?
I'm pretty sure it worked for me.
Thanks in advance!
[0] http://releases.ubuntu.com/groovy/ubuntu-20.10-live-server-amd64.iso
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Hi Po-Hsu Lin, I think AHCI has no native support for EEH; the last news
I found is an attempt to include such support from 2015, but got denied
upstream [0]. When a driver has no native support, EEH works by using
what is called the hotplug approach, which is to PCI-remove the device.
When it come
IIRC I was able to use the parameter Dimitri suggested on Groovy ISO, but it
didn't work in Focal 20.04.1 ISO. That said, we now have Ubuntu 20.04.2 ISO -
can you give it a try Sebastian, with "fsck.mode=skip" set?
This is the link for the new ISO:
http://releases.ubuntu.com/focal/ubuntu-20.04.2
requests/7
** Affects: makedumpfile (Ubuntu)
Importance: Undecided
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Tags: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Public bug reported:
Nividia integrated card GeForce 6150 SE
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libnvidia-common-450 450.102.04-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
these patches,
hypothetically it would affect SKB segmentation, the net/core code - a
bad check could case an oops in this code or they could present a pretty
small overhead due to more checks in the hot path.
** Affects: linux-azure (Ubuntu)
Importance: Medium
Assignee: Guilherme
Yeah..I need the full output. A suggestion: you seems to have 2 devices
(sda and sdb) at the kdump failure point, right? So, you could try to
mount one of them, and save the dmesg, like "dmesg > /mnt/dmesg.kdump" .
That'd be perfect!
Thanks again
--
You received this bug notification because you
Hi Anders, I really appreciate your debug data, thanks a bunch for
buying the PS2 adapter, very useful. So, seems you are observing an
issue with the SATA controller. Could you collect a dmesg from the kdump
environment, in this minimal "(initramfs)" shell?
Also, thanks for the previous data - I f
=> Medium
** Changed in: linux-azure (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Groovy)
Importance: Medium => High
** Changed in: linux-azure (Ubuntu)
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug noti
Public bug reported:
So I have this issue were I downloaded the gamemode extension a long
time ago and hade no issue. But in the past month I have been getting
these errors in Gnome Logs being spammed hundreds of times
https://github.com/gicmo/gamemode-extension/issues/35
Object .Gjs_gamemode_ch
Public bug reported:
hi
I have a Dell notebook with Ubuntu 18.04 preinstalled
I then installed a MTA
So now every day the root user receives this email
Subject: Anacron job 'cron.daily' on [...]
/etc/cron.daily/popularity-contest:
/etc/cron.daily/popularity-contest: 21: .: Can't open
/etc/pop
** Description changed:
- To be filled - I'm just reserving the LP number for now.
+ [Impact]
+ * Currently linux-kvm derivative doesn't have CONFIG_PCI_MSI (and its
dependency options) enabled. The goal for such derivative is to be minimal and
boot as fast as possible in virtual environments, h
Just for reference version I am using is
$ etherwake -v
etherwake.c: v1.09 11/12/2003 Donald Becker, http://www.scyld.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858112
Title:
Etherwake is
I think it is working fine.
By default it assumes your network interface exists i.e. eth0, otherwise
you'll get "SIOCGIFHWADDR on eth0 failed: No such device" response
However on my installation 20.04.2 LTS, my network interface is
enp4s0f0.
Try:
$ sudo etherwake 00:11:22:33:44:55 -i enp4s0f0
Public bug reported:
To be filled - I'm just reserving the LP number for now.
** Affects: linux-kvm (Ubuntu)
Importance: Medium
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Affects: linux-kvm (Ubuntu Xenial)
Importance: Medium
Assignee: Guil
In fact Anders, I just thought of a potential alternative issue, so do
you mind to run a 3rd test?
(c) After running tests (a) and (b) from the last comment, please boot
the machine and edit the file "/etc/default/grub.d/kdump-tools.cfg",
changing the crashkernel parameter there to be exactly
"cra
Hi Anders, thanks for your testing. You can show all the initrd scripts
debug output to console, for that you'd need to add the kernel parameter
"debug=vc" for example. But I don't suggest to do that here, since you
seem not able to capture the full console log in plain/text form.
Pictures/snapshot
kdump-config unload
rm -f /var/lib/kdump/initrd.img*
sed -i 's/MODULES=dep/MODULES=most/g' /etc/kernel/postinst.d/kdump-tools
kdump-config load
ls -lh /var/lib/kdump/initrd.img*
The first command will show you the current kdump initrd images you
have, then next commands delete them and r
I tried running this again after installing apport with the following
result:
do-release-upgrade
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,248 kB]
Fetched 1,248 kB in 0s (0 B/s)
authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg'
extracting
Public bug reported:
attempting to upgrade from 16.04 to 18.04.5 on Linode
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.7 LTS
Release:16.04
Codename: xenial
ran all updates and upgrades and rebooted before I started - fatal error
** Also affects: linux (Ubuntu Linaro Evaluation Build)
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/1063895
Title:
arm64 support to generate linux-sourc
apt update then apt upgrade fixed the problem for me about four days
ago. Thank you for fixing this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905519
Title:
Object St.Bin (0x565425162c80), has
I made a duplicate bug report. The reply to me to post comments here in
this bug report instead. The specs for my bug report is here:
https://bugs.launchpad.net/bugs/1912816
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Changed in: linux-azure (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux-azure (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the report and fix Stefan! Although the LP is a bit old, I
think worth to mention here the patches that fix boths issues (the
"Unknown type (Reserved) while parsing" message and the "ELF core
(kcore) parse failed" bug) - both present in kexec-tools as fixes due to
Linux kernel modificati
System:Host: BDXR-2ML Kernel: 5.10.4-051004-generic x86_64 bits: 64
Desktop: GNOME 3.38.1
Distro: Ubuntu 20.10 (Groovy Gorilla)
Machine: Type: Laptop System: Dell product: G5 5505 v: 1.5.0 serial:
#
Mobo: Dell model: 0YHTJ7 v: A00 serial: UEFI:
I have a Dell G5 15 SE (Gaming Laptop). The Laptop is so new that I can
only install Ubuntu with the current config: Kernel 5.10 (has the AMD
Radeon GPU drivers).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Public bug reported:
Journalctl -f repeately shows every 1 to 2 seconds:
Object St.Bin (0x558f64771240), has been already deallocated — impossible to
set any property on it. This might be caused by the object having been
destroyed from C code using something such as destroy(), dispose(), or remo
*** Bug 1684528 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586822
Title:
Ability to set default save destination for new bookmarks
To manage noti
** Description changed:
Hello everyone,
- I'm a KDE neon user and but noticed that on my installation, the
- required hard disc space keeps increases after each kernel updates. The
- reason is that after installing a new kernel, old one's files are kept
- in '/usr/lib/modules/X.X.X-XX-generic
The bug is not yet actionable, because a decision was not achieved yet.
The team working on 2020H2 bookmarks improvements wanted to complete
collecting users feedback and telemetry before evaluating further steps.
Thus, while I'm in favor of this change, we should at least wait the end
of that proj
Frameworks: 5.78.0
Plasmashell: 5.20.80
QT: 5.15.2
I don't have this issue anymore.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1759328
Title:
plasmashell crash when changing d
Public bug reported:
Hello everyone,
I'm a KDE neon user and but noticed that on my installation, the
required hard disc space keeps increases after each kernel updates. The
reason is that after installing a new kernel, old one's files are kept
in '/usr/lib/modules/X.X.X-XX-generic/' and '/usr/sr
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+bug/1907887/+attachment/5442903/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907887
Title:
Old kernel f
That's interesting, I just performed your suggested test, and I couldn't
reproduce - it's a fresh Ubuntu 20.04 install, running MATE (not KDE!)
and GNU screen 4.8.0-1. After closing the terminal, I've opened another
one and "screen -x" worked fine, as expected.
Could you try to use MATE / Gnome to
501 - 600 of 7567 matches
Mail list logo
