Public bug reported:
Overview of changes in simple-scan 3.36.3
* Change the size of the paper to avoid visual glitches.
* Disable possibility of scanning if no device is found, to avoid unnecessary
errors.
Overview of changes in simple-scan 3.36.2.1
* Revert the higher bit depth text
From: boun...@canonical.com on behalf of Daniel van
Vugt <1883...@bugs.launchpad.net>
Sent: 11 June 2020 19:54
To: robharper22...@outlook.com
Subject: [Bug 1883092] Re: Gnome Shell freeze
Please also wait until the freeze happens again and then when it is
"back
** Attachment added: "settings.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1883092/+attachment/5384390/+files/settings.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883092
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1883092/+attachment/5384389/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883092
I have the same issue on Ubuntu 20.04 on a Macbook 13" Retina and a PC with 4K
27" Monitor, both scaling at 200%.
Im using an AppImage of Gimp 2.10.*, actual 2.10.20.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Gentle bump to raise visibility. If more information is needed, please
let me know.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875199
Title:
[NUC8CCHK][HDA-Intel - HDA Intel PCH,
Hi Daniel,
you wrote:
Am 08.06.20 um 08:58 schrieb Daniel van Vugt:
> The disk partition 'sda4' is slow because it seems to have filesystem
> errors. You should open the 'Disks' app to try and check and repair it.
> When that's fixed, please let us know if you still have any issues and
> if so
Public bug reported:
the computer will freeze everything but mouse and fail to boot back up
for around 30 minutes after
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
Public bug reported:
This is one of the reasons I went from Ubuntu MATE 19.10 to 18.04. The
updates broke the old code which allowed mounting Android Tablets.
Again. New code breaks old code. Not enough regression testing before
releases.
Also got error message:
robert@A88XM-A:~$ ubuntu-bug
Live USB fails to boot or provide command line for submitting log file.
I am attaching a video (excuse the poor quality) that captures the load
sequence. Hopefully this is insightful enough for helping to
troubleshoot.
** Attachment added: "Loading screen capture"
While the system is booted into Linux Mint 19.3 (with audio working
properly), the kernel version is reported as:
Linux NUC8CCHK 5.3.0-53-generic #47~18.04.1-Ubuntu SMP Thu May 7
13:10:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
(I think the kernel version may have been updated slightly as a
Will do.
Rob
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863672
Title:
The 'new' persistent live method starting in 19.10 no longer works
To manage notifications about this bug go to:
I changed the file name from casper-rw to writable and now it works. Thanks.
Took me 5 days to realise there was a bug :)
Rob
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863672
Title:
The 'new'
I have also had this persistence problem with ubuntu 20.04.
Casper will not load a file labelled Casper-rw. It does use a partition
labelled Casper-rw.
Ubuntu 19.04 persistence works with files and partitions labelled casper-rw.
Rob
--
You received this bug notification because you are a member
1969] Re: apparmor profile for libvirtd/libvirt-daemon needs
> fixing
>
> @Robert - you said you see that since an upgrade to 20.04 - to what
> extend could you try other older libvirt versions?
>
> --
> You received this bug notification because you are subscribed to the bug
r libvirtd/libvirt-daemon
> needs fixing
>
> On Mon, Jun 8, 2020 at 11:01 AM Robert Dinse <1881...@bugs.launchpad.net>
> wrote:
>
>> No these servers are in service providing services to people so I can't
>> just reboot at my leisure.
>>
>
> Too b
No these servers are in service providing services to people so I can't
just reboot at my leisure.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not
It may or may not be relevant but I am using a 5.7.0 kernel compiled
from mainline kernel.org source.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not
I attempted the process you describe, however I cannot find any kernel
version which allows for the audio output to work within Ubuntu 20.04.
To reiterate, when testing the system with Linux Mint 19.3 with kernel
version 5.3.0-51 #44-18.04.2-Ubuntu sound works properly.
I used these instructions
Public bug reported:
lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04
systemd-analyze time
Startup finished in 5.406s (kernel) + 1min 8.195s (userspace) = 1min 13.601s
graphical.target reached after 1min 7.513s in userspace
systemd-analyze blame
28.124s
Thank you, Hans.
Regards,
Bob
On Sun, Jun 7, 2020 at 12:35 PM Hans Joachim Desserud <
1882...@bugs.launchpad.net> wrote:
> Then I don't know I'm afraid. I've marked this as also affecting gnome-
> software for someone to take a look at it from that angle.
>
> ** Also affects: gnome-software
On Sun, Jun 7, 2020 at 10:25 AM Hans Joachim Desserud <
1882...@bugs.launchpad.net> wrote:
> >After searching for Calibre on Ubuntu Software and finding the page, I
> pressed the "Install" button.
>
> Ok, have you tried to remove the package through Ubuntu Software?
Yes.
> Is it
> still listed
> Subject: [Bug 1881969] Re: apparmor profile for libvirtd/libvirt-daemon needs
> fixing
>
> Christian: do you think it's worth trying to emulate an actual hardware
> controller instead of using virtio-scsi in your nested VM test setup?
> Maybe sys_rawio is not used with virtio-
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800)
I will be rebooting one of the physical hosts in a little more than an
hour, I'll disable auto-start and try it.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human
I am simply using virt-manager to create virtual machines, I've got
maybe half a dozen on a box, and then after a reboot they are set to start
automatically and dmesg will give me those messages. This is under Ubuntu
20.04, I can not swear they were not happening earlier but I did not notice
On Thu, Jun 4, 2020 at 4:30 PM Hans Joachim Desserud <
1882...@bugs.launchpad.net> wrote:
> >Package 'calibre' is not installed, so not removed
>
> That usually indicates the package isn't installed or already removed.
> How did you install calibre?
>
After searching for Calibre on Ubuntu
I am going to Create a small execute file that will run when OS starts
eventually because it seems to stop the crash i have an old school game
running in the background seems to prevent the crash for the most part
still does crash after 8 hrs or so, Not a real fix but whatever works
right lol :)
Speaking of cloud-images generally I propose the following:
* Images in the ubuntu-cpc project by default should boot with an initramfs.
* Revert the livecd-rootfs change which "Unconditionally set
GRUB_FORCE_PARTUUID in cloud images"
* Images with custom kernels can boot without an
I've opened a track for livecd-rootfs where the minimal image is defined
and I'm going to close the cloud-images portion.
But I will add that the images themselves set the expectation about what
it is to be considered minimal as:
"This system has been minimized by removing packages and content
Here are some Information from the Windows Device-Manager and Eventlog.
Am Donnerstag, den 04.06.2020, 09:44 + schrieb Kai-Heng Feng:
> Can you please take a screenshot under Windows, shows what the
> touchpad
> looks like in Device Manager?
>
** Attachment added: "elan-touchpad-data.txt"
ruomini@ruomini-XPS-13-9370:~$ sudo apt purge calibre
[sudo] password for ruomini:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'calibre' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
Public bug reported:
When I try to remove Calibre, I get an error "No packages to remove".
Same thing with E-book editor, LRF Viewer and E-book viewer. Is this
malware?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: calibre (not installed)
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic
Public bug reported:
Libvirtd is trying to use a capability being denied it by apparmor.
[474656.842239] audit: type=1400 audit(1591211959.677:101):
apparmor="DENIED" operation="capable" profile="libvirtd" pid=3393444
comm="libvirtd" capability=17 capname="sys_rawio"
ProblemType: Bug
Public bug reported:
If the NFS server reboots, sometimes client servers fail to re-establish
the NFS mount properly. This is using NFS v4.2. The client machine
will hang if I try to do a df when an NFS mount is in this condition.
Attempting to access a file will likewise hang indefinitely.
The system does not have Windows installed at present, however I am
happy to install Windows 10 if it helps the investigation.
If you can please just provide instructions for what you would like to
me do from within Windows I will do my best to provide the information
promptly.
* Just a quick
I added a -d flag to the invocation of perl in the shebang line of
/usr/share/lintian/frontend/dplint Here is what I got:
# lintian --help
Loading DB routines from perl5db.pl version 1.55
Editor support available.
Enter h or 'h h' for help, or 'man perldebug' for more help.
I'm moving this from cloud-images to lintian, this is not an issue
specific to the image itself.
** Changed in: cloud-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Eoan arm64 container on focal amd64 host does not recreate this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881217
Title:
arm64v8 focal: lintian will get stuck with it
To manage
Gentle bump to raise visibility. In more information is needed please
let me know.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875199
Title:
[NUC8CCHK][HDA-Intel - HDA Intel PCH,
Public bug reported:
I have a Desktop PC with MSI PRO B450-A PRO Motherboard and CPU Intel
Core AMD RYZEN 3 3200G 4-Core 3.6 GHz, and RAM CORSAIR Vengeance LPX
16GB (2 x 8GB) 288-Pin DDR4 SDRAM.
OS is Ubuntu 18.04 LTS. Current kernal 5.3.0.53.
This system has been in operation normally for
Sorry i am trying to do this but this crashes are almost instant when i
log in now it was never this bad before maybe 2 3 times a day now it
restarts 30 plus times day not kidding crazy i know my dedication to not
use windows :)
--
You received this bug notification because you are a member of
It doesnt restart when idling or in Bios or when in safe graphics
install on Main pc Or laptob but then whence login crash, also i cant
access terminal with crl alt f3 this is crashing. Couple obseervations
im posting to keep my self sane at this moment :)this was my default
maybe ic an fix
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1881445/+attachment/5379133/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt.txt"
https://bugs.launchpad.net/bugs/1881445/+attachment/5379132/+files/CurrentDmesg.txt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@fermulator Thanks will keep that in Mind But I am doing Single Boot
only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848496
Title:
[zfs-root] "device-mapper: reload ioctl on
May 31 02:16:41 IceStar gnome-shell[3143]: Telepathy is not available,
chat integration will be disabled.
So ya i was searching thru the log and found this can someone
explain to me on a fun basis what this exactly is lol?
--
You received this bug notification because you are a member
And all the other menues work except that one... Oh well, I can find
the apps I need and edit menus myself.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human
I don't use gnome, I use Mate as I stated and it still has the layout
you describe, AND it worked in 19.10. There is a file just called
"studio.menu" there. There is no lone in it with DefaultMergeDirs in it.
On Sat, May 30, 2020 6:49 pm, Len Ovens wrote:
> the ubuntustudio menu relies on the
Ok, ignore the bug. It worked fine on 19.10 and doesn't on 20.04, supported or
not. Ubuntu is
getting to suck like Redhat, perhaps time to look for another distro.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Prior to 20.04 I had Ubuntustudio installed but I used Mate desktop. On Mate
there was a
Ubuntustudio menu under the Apps menu. That disappeared when I upgraded to
20.04, an in-place
upgrade. I re-installed ubuntustudio-menu and ubuntustudio-menu-add, but it
still does
Public bug reported:
Random Crashes
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "syslog3May302020.txt"
https://bugs.launchpad.net/bugs/1881445/+attachment/5378896/+files/syslog3May302020.txt
--
You received this bug
Link to postfix-users archive:
http://postfix.1071664.n5.nabble.com/postfix-tls-deploy-server-cert-
fails-with-quot-can-t-shift-that-many-quot-td106183.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Below is a reply from postfix-users. Works perfectly for me.
--
Below is a patch. I find that the handling of this differs a lot
among shell implementations, from terminating to ignoring.
Wietse
diff -ur /var/tmp/postfix-3.6-20200523/conf/postfix-tls-script
conf/postfix-tls-script
---
I met the issue when installing packages from a private PPA of
Launchpad. Hope this would be helpful to reproduce the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801338
Title:
apt fails
device-mapper: reload ioctl on osprober-linux-sda7 failed: Device or resource
busy
Command failed.
done
apt purge os-prober worked for me not getting any errors when updating grub now
thanks
one more thing knocked of the list YAY!
--
You received this bug notification because you are a
Ah. I'll report it to postfix-users as recommended.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881196
Title:
postfix tls deploy-server-cert fails with "can't shift that many"
To manage
Public bug reported:
lsb_release -rd
Description:Ubuntu 18.04.4 LTS
Release:18.04
postfix:
Installed: 3.3.0-1ubuntu0.2
Candidate: 3.3.0-1ubuntu0.2
Version table:
*** 3.3.0-1ubuntu0.2 500
500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic-updates/main
amd64
Thanks. I deliberately wasn't going to use cairo instead of libswscale
as I read it may cause performance issues for image scaling. I didn't
test it so some testing is needed to see if it matters or is even used
with guacamole.
--
You received this bug notification because you are a member of
Thanks much appreciated. I've got a development build from the freerdp-
daily PPA but it's pretty clear that the symbols still need appropriate
mapping. The Debian build has some it for the 2.1.0 build they started.
It's clearly some kind of backwards compatibility logic but I'm unclear
on intent.
*** This bug is a duplicate of bug 1872778 ***
https://bugs.launchpad.net/bugs/1872778
Thank you Simon Déziel you saved my life!!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866974
Title:
** No longer affects: cloud-images/trunk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569237
Title:
vagrant xenial box is not provided with vagrant/vagrant username and
password
To manage
FYI a Debian developer has started on freerdp 2.1.0, nothing is released as of
yet. I took a look at all the symbols in that package and was taking the wrong
approach so I didn't use my attempt.
The freerdp-daily repository guys have also kindly packaged 2.1.1.
--
You received this bug
Public bug reported:
Whether I select large or huge, same size results, huge no longer gives
me a very large font which owing to my crappy eyesight is sometimes
helpful.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xterm 353-1ubuntu1
Uname: Linux 5.6.0 x86_64
.tmp.unity_support_test.1:
Hi, which information do you need?
Am Dienstag, den 26.05.2020, 06:29 + schrieb You-Sheng Yang:
> Hi, actually we cannot find any hint for your touchpad hardware from
> the
> logs. Do you have Windows installed on the same machine that touchpad
> is
> working? We may need some info from that.
Changed to i915drmfb now HDA HDMI loads.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880494
Title:
i915 hdaudio no codac bind
To manage notifications about this bug go to:
Hey,
the latest mainline kernel does not solve the problem.
regards,
robert
Am Freitag, den 22.05.2020, 08:15 + schrieb Kai-Heng Feng:
> Please test latest mainline kernel:
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc6/
>
>
> ** Changed in: linux (Ubuntu)
Confirmed in kernel mailing list
** 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/1880494
Title:
i915 hdaudio no codac bind
To
Public bug reported:
ubuntu focal x86_64 linux-image-5.4.0-31-generic
i915 is a module SND_HDA_I915 is not.
For hdaudio to bind to codec HDA_I915 must be module.
Alsa dev on kernel mailing list gave this answer.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
In addition to the two-keyboards thing, I'm also experiencing this
problem using the Sidewinder X4 keyboard when holding more than 6
simultaneous keys. According to xev, this keyboard also sends
MappingNotify events when it gets to that point.
--
You received this bug notification because you
@Hui,
Thank you for looking deeper into the problem, and for your explanation.
I tried disconnecting and reconnecting the speaker to the audio output
jack as you suggested, however it did not change the behavior. The
'Dummy Output' remains, and no sound is heard.
@Kai, I added the PPA you
@kaihengfeng, not sure how to capture dmesg, as the boot process never
completes preventing me from accessing a command line. Also, I am
unable to switch to another TTY session. Can you please provide guidance
or direct me to a article that explains how to capture the log?
--
You received this
I suspect freerdp2 was derailed in politics much like the stalls and eventual
removal of a package for guacamole-server. What is currently deployed in Ubuntu
focal is a alpha development snapshot of freerdp2 2.0.0 which is buggy to the
point of being unusable for Apache guacamole and has
Public bug reported:
Ubuntu's version of dracut is now 2 years old and has since been superseded by
2 upstream releases (Ubuntu: 048, Upstream: 050). Please get the package
updated so users can make use of the new code as foundation to develop modules.
In particular, a dracut PR to add
Public bug reported:
Fresh Ubuntu 18.04.4 LTS bionic installation.
Nouveau driver.
One DVI cable attached directly to the graphics card, and one DVI + one VGA
attached to the motherboard.
When I attempted to open "Display" settings the x-org session crashes and
reverts to the login screen.
i installed 440 and can't log in and create this apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876517
Title:
log in doesn't work
To manage notifications about this bug go to:
** Attachment added: "apport.xorg.44vc11yz.apport"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1876517/+attachment/5375036/+files/apport.xorg.44vc11yz.apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
How can i collect this data for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876517
Title:
log in doesn't work
To manage notifications about this bug go to:
** Summary changed:
- log in not works
+ log in doesn't work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876517
Title:
log in doesn't work
To manage notifications about this bug go to:
Testing with the the 5.7.0-050700rc6-generic kernel does not change the
behavior. Sound output does not work, and the 'Dummy Output' remains in
the Sound section within the Settings application.
When testing the system with Linux Mint 19.3 with kernel version
5.3.0-51 #44-18.04.2-Ubuntu sound
Public bug reported:
The Touchpad is not detected on any Ubuntu Live or installed Version
from 16.04 to 20.04.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-31-generic 5.4.0-31.35
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic
** Also affects: nvidia-graphics-drivers-435 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
$ pyvenv
Command 'pyvenv' not found, but can be installed with:
sudo apt install python3-venv
$ sudo apt install python3-venv
Reading package lists... Done
Building dependency tree
Reading state information... Done
python3-venv is already the newest version
Public bug reported:
Get error while installing updates
Ubuntu 20.04 LTS
grub-efi-amd64-signed:
Installed: 1.142+2.04-1ubuntu26
Candidate: 1.142+2.04-1ubuntu26
Version table:
*** 1.142+2.04-1ubuntu26 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
Aha, thanks Daniel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851162
Title:
nvidia-drivers-390 fail to build with kernel 5.3
To manage notifications about this bug go to:
This bug is not fixed. I have upgraded from 19.10 to 20.04 LTS
I had installed nvidia-driver-440, but due to this bug I downgraded to
nvidia-driver-390. I get exactly the same issue. All my packages are up-
to-date.
The output:
DKMS make.log for nvidia-390.132 for kernel 5.4.0-29-generic
I tried booting in safe graphics mode. It gets stuck in an endless
loop:
watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u8:3:194]
rcu: INFO: rcu_sched self-detected stall on CPU
rcu: $0-...: (14999 ticks this GP) idle=736/1/0x4002
softirq=5356/5356 fqs=7398
[FAILED]
I created a live USB of my system using systemback before trying to
upgrade from 19.10 to 20.04. My live USB backup works fine. I tried a
Fedora 31 live USB and it works fine. I also used different methods to
create the 20.04 Live USB thinking it might have been a corrupt iso. I
tested the
I have identified the same issue. Parsing a relatively small file may
result in a calloc failure because lh_table_new attempts to allocate an
incorrectly size block of memory. In my case it attempted to allocate
over 68 GiB in a single allocation.
The cause seems to be the changes in the CVE
Unable to load kernel to generate log file.
** 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/1878726
Title:
Live USB Installer not
Public bug reported:
Live USB made from ubuntu-20.04-desktop-amd64 fails to boot. System
hangs with watchdog: BUG: soft lockup - CPU# and rcu: INFO: rcu_sched
self-detected stall on CPU.
System specs:
Intel(R) i7-7500U running AMD discrete graphics
Have tested the Live USB on other systems
Gentle bump to raise visibility. In more information is needed please let me
know.
In the interim I tested the behavior with Linux Mint 19.3, and audio output
works correctly when using that distribution.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Problem still exists even after disabling apparmor completely:
May 14 09:46:18 dc sh[4241]: ../../../../lib/isc/unix/socket.c:3361:
INSIST(!sock->pending_send) failed, back trace
May 14 09:46:18 dc sh[4241]: #0 0x7fdeeb0dca4a in ??
May 14 09:46:18 dc sh[4241]: #1 0x7fdeeb0dc980 in ??
May 14
Works for me as well. Thank you very much Vincent!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878005
Title:
Chrony crashes on install from raspberry pi 2
To manage notifications about this bug
execve("/usr/sbin/chronyd", ["chronyd", "-d", "-F", "-1"], 0xbe9ae644 /* 24
vars */) = 0
brk(NULL) = 0x20e5000
uname({sysname="Linux", nodename="dc2", ...}) = 0
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb6ff8000
** Package changed: ubuntu => ubuntu-ubuntu-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878445
Title:
Ubuntu 20.04 arm64 server-cloud image hits kernel panic but boots
successfully on
Public bug reported:
This is the image we are using:
https://cloud-images.ubuntu.com/releases/20.04/release/ubuntu-20.04-server-cloudimg-arm64.img
When the image boots, it first hits a kernel panic. Then the Grub menu
appears, counts down and
successfully boots.
>From looking a bit at the
root@dc2:/etc/chrony# chronyd -d -d
2020-05-13T13:13:47Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC
+PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG)
2020-05-13T13:13:47Z Frequency -2.286 +/- 1.012 ppm read from
/var/lib/chrony/chrony.drift
2020-05-13T13:13:52Z Selected
root@dc2:/etc/chrony# systemctl status chrony
● chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor
preset: enabled)
Active: failed (Result: protocol) since Wed 2020-05-13 15:07:23 CEST; 21s
ago
Docs: man:chronyd(8)
Same problem. Chrony starts without problems using "chronyd -d -d" as
root.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878005
Title:
Chrony crashes on install from raspberry pi 2
To manage
801 - 900 of 37084 matches
Mail list logo
