Confirmed, thanks for your work on this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To manage notifications about this bug go
Both problems persist on 20200522.0.0, here is the kernel panic and
reboot:
[0.883971] VFS: Cannot open root device "PARTUUID=43931bda-01" or
unknown-block(0,0): error -6
[0.885744] Please append a correct "root=" boot option; here are the
available partitions:
[0.887371] Kernel
Yes, there is some lag. Although the image is named 0522, it was not
available until the 25th of May, note the created message from your
link:
"v20200522.0.0 currently released version
This version was created about 24 hours ago."
I did test the 0518 focal image and it was not fixed, 0522 is
Confirmed, it is available now and fixes 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/1873506
Title:
ubuntu/focal64 fails to mount Vagrant shared folders
To manage notifications about
New images do not appear to be available quite yet, still getting the
May 18 image.
$ vagrant box update
==> default: Checking for updates to 'ubuntu/focal64'
default: Latest installed version: 20200518.0.0
default: Version constraints:
default: Provider: virtualbox
==> default: Box
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1874453/+attachment/5367917/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1874453/+attachment/5367916/+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/1874453
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1874453/+attachment/5367920/+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/1874453
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1874453/+attachment/5367914/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1874453/+attachment/5367915/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1874453/+attachment/5367919/+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/1874453
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1874453/+attachment/5367921/+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/1874453
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1874453/+attachment/5367918/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1874453/+attachment/5367913/+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/1874453
Title:
apport information
** Tags added: apport-collected uec-images
** Description changed:
Using `ubuntu/focal64` version `20200423.0.0`, the boot process is
extremely slow and the box always reboots once before completing a
successful boot. With default settings, this causes a timeout in
Same behavior on eoan, both the one-off kernel panic and slow boot
without overriding the console settings.
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
Ok, I tested 5.3.0-52-generic on eoan, the modules are present, the
system boots and runs normally.
vagrant@ubuntu-eoan:~$ ls -1
/lib/modules/5.3.0-52-generic/kernel/virtualbox-guest/*
/lib/modules/5.3.0-52-generic/kernel/virtualbox-guest/vboxguest.ko
** Tags removed: verification-needed-focal
** Tags added: 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/1873506
Title:
ubuntu/focal64 fails to mount Vagrant shared folders
Not sure how to test this as requested by the bot. I don't think just
enabling proposed on an existing published image is sufficient. Are
there proposed cloud image builds posted somewhere?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm pretty sure the java-7-openjdk updates are responsible for this
behavior:
Start-Date: 2012-09-12 16:46:50
Commandline: apt-get dist-upgrade
Upgrade: openjdk-7-doc:amd64 (7~u3-2.1.1~pre1-1ubuntu3,
7u7-2.3.2-1ubuntu0.12.04.1), openjdk-7-jdk:amd64 (7~u3-2.1.1~pre1-1ubuntu3,
I should have mentioned you can restore the files with:
$ sudo apt-get install --reinstall tzdata-java
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050404
Title:
Causes several facilties of
Serge,
Sorry, I should have provided more info. I'm running the Kubuntu
variant and did a distribution upgrade from Karmic to Lucid, after which
this problem started occurring.
Turns out I was sloppy in my checks, the pulseaudio package was not
installed. I was thrown off by the fact
Serge,
Sorry, I should have provided more info. I'm running the Kubuntu
variant and did a distribution upgrade from Karmic to Lucid, after which
this problem started occurring.
Turns out I was sloppy in my checks, the pulseaudio package was not
installed. I was thrown off by the fact
I have this same problem:
$ dpkg -s pulseaudio qemu-kvm | grep -E '^(\s*$|Package|Version)'
Package: pulseaudio
Version: 1:0.9.19-0ubuntu4
Package: qemu-kvm
Version: 0.12.3+noroms-0ubuntu9
I get the errors shown in the original report and also some additional
'Internal Error' ones
I have this same problem:
$ dpkg -s pulseaudio qemu-kvm | grep -E '^(\s*$|Package|Version)'
Package: pulseaudio
Version: 1:0.9.19-0ubuntu4
Package: qemu-kvm
Version: 0.12.3+noroms-0ubuntu9
I get the errors shown in the original report and also some additional
'Internal Error' ones
I can confirm this bug in lucid.
Relevant snippets:
$ apt-cache show python-pip | grep -E '^(Package|Version|Depends|Conflicts)'
Package: python-pip
Version: 0.3.1-1ubuntu2
Depends: python, python-central (= 0.6.11), python-pkg-resources |
python-setuptools ( 0.6c8-1)
$ dpkg --get-selections
I sometimes experience a similar problem, although I have an nVidia
graphics card. The stack in the attached KDM log appears close, but not
exactly the same, as the one posted in #5.
For me, this seems to be proceeded by my up key no longer working in
KDE. If I then logout, I get a blank black
Well, it's a few kernels later and I'm able to successfully connect to
the router in this report as well as several others I've tried that use
WEP. It should be safe to close this as resolved.
--
Wireless with WEP fails to associate with AP after jaunty to karmic upgrade
With this package (Version: 1.6.5dfsg-1ubuntu1~hardy1~andersk1), I get the
following warning:
---
ATTENTION! Your password for authentication realm:
http://XXX.com:80 XX
can only be stored to disk unencrypted! You
Public bug reported:
After upgrading from jaunty to karmic, I can no longer connect to my
wireless router using WEP managed by NetworkManager. It authenticates
but fails to associate. Thinkpad T500 with an Intel 5300 wireless card,
logs should cover the upgrade which was a couple hours old.
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/34634220/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/34634221/AplayDevices.txt
** Attachment added: BootDmesg.gz
http://launchpadlibrarian.net/34634223/BootDmesg.gz
** Attachment
I forgot to mention, this looks a lot like bug #404433 except that one
explicitly says WEP is working.
--
Wireless with WEP fails to associate with AP after jaunty to karmic upgrade
https://bugs.launchpad.net/bugs/463904
You received this bug notification because you are a member of Ubuntu
Bugs,
Adding daemon.log
** Attachment added: /var/log/daemon.log
http://launchpadlibrarian.net/34634489/daemon.log
--
Wireless with WEP fails to associate with AP after jaunty to karmic upgrade
https://bugs.launchpad.net/bugs/463904
You received this bug notification because you are a member of
Adding /var/log/messages
** Attachment added: /var/log/messages
http://launchpadlibrarian.net/34634565/messages
--
Wireless with WEP fails to associate with AP after jaunty to karmic upgrade
https://bugs.launchpad.net/bugs/463904
You received this bug notification because you are a member of
I just started having this problem in hardy (manifested by Java) after
an update today (2009-07-14). The sed/XINERAMA workaround suggested by
others earlier worked for now.
Here are the packages I upgraded, it began immediately afterward:
2009-07-14 09:12:52 upgrade libdbus-1-3
35 matches
Mail list logo
