Can you run and attach the output tarball on the target system where you
see this fail:
cloud-init collect-logs
With respect to your use-case; cloud-init does not directly control what
packages do at install time. Some package may require post-install
configuration, or are not typically
Please move this back to New after you've attached the cloud-init
collect-logs output tarball.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm marking the cloud-init task invalid for now.
As mentioned in the other bug[1]; cloud-init is not running too late;
rather scripts not provided to cloud-init are not waiting for cloud-init
to complete its execution. If your scripts are using cloud-init status
--wait before executing or
See also:
https://github.com/flatpak/flatpak/issues/3660
** Bug watch added: github.com/flatpak/flatpak/issues #3660
https://github.com/flatpak/flatpak/issues/3660
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The upstream bug is closed as working-as-designed, but this is impactful
to anything that expects ```df``` to exit 0 as a non-root user.
ex.
me@here:~$ df -h
df: /run/user/1000/doc: Operation not permitted
Filesystem Size Used Avail Use% Mounted on
tmpfs
Public bug reported:
I am a novice user attempting to get an RX 6800-XT GPU working on Ubuntu
20.04. I'm using Ubuntu 20.04 because it's recommended by the official
AMD driver installer.
The RX 6800-XT requires kernel 5.10 or later. I have updated to kernel
5.10.0-rc6 using the mainline kernel
* Christian Dohm <1906...@bugs.launchpad.net> [2020-11-29 15:50]:
> Public bug reported:
>
Thank you for filing a bug.
> I've created a 'network-config' file with Terraform's yamldecode() function
> that contains (btw. I've tried with the version being a Number w/o quotes and
> as well as a
Please open the new bug and provide a link so I can follow the progress
and test the solution
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849142
Title:
appindicator extension slows down GUI
Status file too
** Attachment added: "status.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+attachment/5435346/+files/status.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Done! I see
Nov 18 14:24:37 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: discord1,
Impossible to lookup icon for 'discord1_33-panel' in path
/tmp/.org.chromium.Chromium.PSxy7s
Nov 18 14:24:37 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: unable to
update icon for discord1
Nov 18
Why does the issue still occur with the fix? The severity is lessened
but it is still there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849142
Title:
appindicator extension slows down GUI
sudo apt install gnome-shell-extension-appindicator/focal
seemed to restore it properly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849142
Title:
appindicator extension slows down GUI spamming
After installing the deb (oddly asking me to downgrade to your supplied
version) and logging back in, I was greeted with an error from my HP
printer drivers saying there is no detected system tray and it's unable
to start (attached).
Discord and MegaSync still appear in the tray so I don't know
I'm running Pop OS 20.04 with this bug, I'd be happy to test this if I
knew how to install the patch. Do I just need to enable proposed
packages?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849142
Public bug reported:
grub install fatal error
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion:
** Package changed: linux (Ubuntu) => linux-raspi2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895550
Title:
Ubuntu 18.04.5 release for Raspberry Pi 4 does not boot
To manage
I also could not boot 20.04.1 on a Raspberry Pi 4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895550
Title:
Ubuntu 18.04.5 release for Raspberry Pi 4 does not boot
To manage notifications
Well, it took more than 24 hours for my Pi to crash again, but it did
happen. I wasn't able to capture much of what triggered it as i wasn't
home at the time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After fresh install of hplip and hplip-gui, executable symlinks
/usr/bin/hp* are broken. /usr/share/hplip/*.py are not present, and in
fact, the /usr/share/hplip directory is missing completely. The package
is completely broken.
Here is the output of the package
Ok yup this is almost certainly the issue (when the tunnel is pi is
tunnelling traffic for something other than itself)
My tunnel has been up for 12 hours, no crashes at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@juergh I may have (somewhat) found the trigger.
As previously noted, my internal clients have a static route to the remote
wireguard networks via my raspberry pi. This is defined in my internal router
(Unifi)
ie:
client > router > static route (10.241.0.0/24) to pi eth0 IP > pi > tunnel > VPS
RE IPv6, there is some manual config.
I have each vlan/network assigned a /64. On my pi's they get an address
in that /64 (different networks for eth0 and wlan0) but they do have a
static assignment as well (should have included that earlier:
interface eth0
metric 300
static
So exactly what type of payload triggers the issues, that i cant work
out.
I know the traffic profile, vast majority of it is monitoring related as my VPS
is running grafana/influx and my internal clients are sending data over this
tunnel using telegraf.
There is also a fair bit of ICMP etc
And the most recent crash:
Oct 22 11:44:51 dns1 kernel: [ 3096.793118] [ cut here ]
Oct 22 11:44:51 dns1 kernel: [ 3096.793183] NETDEV WATCHDOG: eth0 (lan78xx):
transmit queue 0 timed out
Oct 22 11:44:51 dns1 kernel: [ 3096.793282] WARNING: CPU: 2 PID: 0 at
Forgot to include:
Raspberry PI:
ubuntu@dns1:~$ uname -a
Linux dns1 5.4.0-1022-raspi #25-Ubuntu SMP PREEMPT Thu Oct 15 13:31:49 UTC 2020
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@dns1:~$
VPS:
root@m21:~# uname -a
Linux m21 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64
Absolutely!
--
My Raspberry Pi sits inside my home network, its config:
eth0:
IP: 192.168.200.11
GW: 192.168.200.1
IPv6: enabled (prefix delegation from ISP)
Metric: 300
wlan0:
IP: 192.168.209.11
GW: 192.168.209.1
IPv6: enabled (prefix delegation from ISP)
Metric: 400
wg0: flags=209
I am also on a 3B+
ubuntu@dns1:~$ cat /proc/device-tree/model
Raspberry Pi 3 Model B Plus Rev 1.3
I dont believe you need anything fancy with IPv6, im not tunneling any v6 and
its occurring with me.
I do have IPv6 enabled on the interface used for tuneling.
Hui Wang, im happy to provide a
@nb This issue is *slightly* different than the other bug related to
missing BootCurrent value.
The previous bug which is fixed in curtin happens when the BootCurrent
value is not present in the efibootmgr output.
This bug has a BootCurrent value, like 0003, however, the Entries
provided by
@Dann
For this firmware bug where we have missing entries; Have you ever
booted this up and had efibootmgr show all of the entries?
Looking at this output here:
BootCurrent: 0003
Timeout: 10 seconds
Same issue, though for some reason the menu entry seem to actually boot
to the ISO just fine, which is just really strange...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812916
Title:
@Dann
OK. That sounds reasonable. For this issue, curtin can (and I think it
makes sense) ignore a BootCurrent value if there is no corresponding
entry; warn in the logs that it's missing, check your firmware, etc...
and proceed if it can.
** Changed in: curtin (Ubuntu)
Importance:
On Thu, Oct 15, 2020 at 10:45 AM Frode Nordahl <1899...@bugs.launchpad.net>
wrote:
> Ryan, thanks for those pointers, will check. I also see in #15 that
> Bionic uses Fallback while Focal uses an actual ds, don't know why
> though.
>
Bah, I *keep* forgetting, that Bion
Looking back at your patch:
Index: curtin-20.1-29-g81144052/curtin/util.py
===
--- curtin-20.1-29-g81144052.orig/curtin/util.py
+++ curtin-20.1-29-g81144052/curtin/util.py
@@ -886,6 +886,7 @@ def get_efibootmgr(target=None):
"""
> I guess it's time for me to ask a question: is it cloud-init that
> renders /etc/netplan/50-cloud-init.yaml? If so where does netplan
> fit in when the difference is how that file is rendered and not
> how it is interpreted. As you can see in #10 the mtu statement is
> not in the file on bionic,
Thanks for the logs Dann,
The error comes from efibootmgr itself; so I don't think this is the
same issue. You can open a new bug; but it still looks like a
firmware/platform issue.
efibootmgr claims there are 5 entries; and at least after a grub
install, there is only one. What happened to
> On the flip side the presence of the MTU key in the OpenStack
> metadata cannot be used as an indicator for intent from either the
> system or the user that the DHCP server should not be providing the
> MTU either.
>
> Looking at the commit that changed the behaviour in OpenStack the
> intent of
> So I would suggest that whenever OpenStack eludes to dynamic configuration
> being in play cloud-init should not write the MTU value into the on-disk
> configuration but let it be configured by dynamic network configuration
> protocol.
>
> What do you think?
I would argue the opposite. The
Version 69 of Dash to Dock fixed this bug, at least in my tests.
Can someone else test if it works?
Disable Ubuntu Dock in Extensions app and install version 69 of Dash to
Dock in extensions.gnome.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
" # curl http://169.254.169.254/openstack/2018-08-27/network_data.json
{"links": [{"id": "tapa035fb68-01", "vif_id":
"a035fb68-010c-42e3-8da7-ea3c36a0d607", "type": "ovs", "mtu": 8942,
"ethernet_mac_address": "fa:16:3e:31:26:f7"}], "networks": [{"id": "network0",
"type": "ipv4_dhcp", "link":
@Dann Thanks.
Can you provide the log without your changes? Or at least the
efibootmgr dump before curtin starts processing things?
> Notice we have no entry for current/0003. I have not inspected the code to
> determine whether or not this is an issue parsing efibootmgr output or the
>
@Jeff I cannot read the canonical pastebin output, can you use
paste.ubuntu ?
re: -updates; MAAS needs to initiate an SRU for archive users of MAAS.
@nb
I don't know for sure. I was told that MAAS snaps would pull curtin
from git master (or the respective release branches).
--
You received
Cancel that. As expected, issue still present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861936
Title:
Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
network load
I *may* be jumping the gun here, but having just installed
5.4.0-1019-raspi this morning, things appear to be good!
Did an upgrade ~ 30 minutes ago (usually i find the issue is triggered
after around 10 minutes or so).
Will update if/when it crashes.
--
You received this bug notification
It appears this was fixed in the upstream development branch:
https://github.com/MayaraCloud/apt-transport-s3/commit/ce0064be41e1ff34f1e4e2cedc48a0cf3fb9d9dd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
wow ok. i actually have a a acer aspire 5 with a 4500u
i couldnt get ubuntu to boot on it so i abandoned it and re installed
windows.
is there a 20.10 iso available for download?
On Mon, Sep 28, 2020 at 4:01 PM Richard Elkins <1891...@bugs.launchpad.net>
wrote:
> This could very well be an issue
Hi Patricia,
You'll need to upgrade MAAS itself. The curtin_userdata is what's sent
to the nodes deploying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895922
Title:
maas could not deploy a
I believe this is a duplicate of:
https://bugs.launchpad.net/curtin/+bug/1876258
This has already been fixed in curtin, you can test with curtin's daily PPA, or
curtin in groovy.
W.r.t uvtool; like MAAS, uvtool should generate serial disk attributes
for all virtio disks by default.
**
I am unable to collect logs because the system fails to boot.
** 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/1895550
Title:
Sending to the kernel team but not sure it belongs with them.
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895550
Title:
Ubuntu 18.04.5 release for
Just a heads up.. Noticed this post digging into the same exact syptoms
with a schiit hel on arch linux. (5.8.8 kernel). I was able to resolve
the lack of audio by installing and using pulsemixer. Using pulsemixer
if you hit f3 (cards) and set the audio source from off to digital
stereo duplex it
Just a heads up.. Noticed this post digging into the same exact syptoms
with a schiit hel on arch linux. (5.8.8 kernel). I was able to resolve
the lack of audio by installing and using pulsemixer. Using pulsemixer
if you hit f3 (cards) and set the audio source from off to digital
stereo duplex it
I downloaded and decompressed the image again and got
`3a156ce4bb81f48876e648d46a7ae6d6` so I am more confident that this is
the correct version of the image.
However, it fails the same way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I decompressed the image again and got the md5
`3a156ce4bb81f48876e648d46a7ae6d6` but I did not try flashing it. It
seems likely it was simply a broken image. I could not find a published
md5 to verify. The files are the exact same number of bytes, though.
--
You received this bug notification
Public bug reported:
I have a Raspberry Pi 4 Model B. I downloaded and flashed the image
`ubuntu-18.04.5-preinstalled-server-arm64+raspi4.img` (md5 =
b75105bf4e27cbcc44dc471becc8907d), which is the currently recommended
release for this hardware on the Ubuntu.com website.
Booting reaches this
** Summary changed:
- Superceded by rtl88x2bu driver
+ Superceded by newer rtl8812au 5.x and rtl88x2bu driver
** Description changed:
The old 8812au driver doesn't support newer hardware and is frequently
- broken with 5.x kernels. The rtl88x2bu driver at
-
Public bug reported:
The old 8812au driver doesn't support newer hardware and is frequently
broken with 5.x kernels. The rtl88x2bu driver at
https://github.com/cilynx/rtl88x2bu is the most up to date version for
this series of hardware which still has no in-kernel driver.
** Affects: rtl8812au
Does this package have an owner? This really needs to be fixed since it
blocks every new user of Ubuntu with this network hardware who has
automatic upgrades enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Seth
Thanks for verifying!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894217
Title:
2.8.2 deploy and commission fails corrupted bootorder variable
detected
To manage notifications about
@ltrager
Any idea why the maas verification for the 20.1 SRU didn't catch this?
curtin's vmtest runs with pristine NVRAM, so we always run with
update_nvram=true otherwise we can't boot into whatever is installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
mwhudson already saw this and fixed in master, though without filing a
bug and no review AFAICT. =(
https://git.launchpad.net/curtin/commit/?id=83944d61e95ea7eb17289625330f0863bec39488
So daily curtin groovy is fixed. This is released in 20.1 so we'll need
to SRU to Xenial, Bionic, Focal.
**
Hi Jeff,
That's great. I'm just pushing this into a ppa for testing:
https://launchpad.net/~raharper/+archive/ubuntu/lp1894217
Groovy should publish any minute now, and I'll copy into
focal/bionic/xenial pockets shortly after.
Please let me know if this fixes things.
--
You received this
@Dan
Just ran into this issue in curtin's vmtest for network_vlan on groovy.
I can confirm that if the netplan config includes the driver match on
the physical interfaces, then the vlans come up just fine.
I was thinking that netplan could inject the driver of the underlying
device into the
Turns out it's unrelated to bcache; it is trivially reproducible:
lxc launch ubuntu-daily:groovy g1 --vm
lxc exec g1 bash
fallocate -l 1024M /swap.img
mkswap /swap.img
swapon --verbose /swap.img
cat /proc/swaps
On the 5.4 kernel that groovy had a few weeks back this works, on daily
(5.8) this
** Summary changed:
- fallocate swapfile has holes on 5.8 ext4 over bcache
+ fallocate swapfile has holes on 5.8 ext4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894910
Title:
fallocate
Public bug reported:
1) Groovy
2)
root@ubuntu:/home/ubuntu# apt-cache policy linux-image-generic
linux-image-generic:
Installed: 5.8.0.18.22
Candidate: 5.8.0.18.22
Version table:
*** 5.8.0.18.22 500
500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100
Thanks for the logs.
They certainly seem to be duplicate entries, so AFAICT, the removal seems
reasonable.
However, removing BootCurrent shouldn't happen as we plan to boot back into
that entry anyhow.
I've got a branch that I'll build and put into a PPA so you can test
here shortly. It does
Thanks for the logs.
** Changed in: curtin (Ubuntu)
Status: Incomplete => In Progress
** Changed in: curtin (Ubuntu)
Assignee: (unassigned) => Ryan Harper (raharper)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi David,
would you be able to attach:
1) efibootmgr -v output (with all of the network entries present? it appears
that there
may be some duplicate entries in the menu; I'd like to confirm that by
examining verbose
output. Specifically Boot -> Boot0003.
Boot* EFI Network 1
were you able to figure it out?
should i post another log?
On Mon, Aug 17, 2020 at 12:46 AM Ryan D wrote:
>
> Thank you. I dont know how i did not see that before
>
> On Mon, Aug 17, 2020 at 12:25 AM Daniel van Vugt <
> 1891...@bugs.launchpad.net> wrote:
>
>>
Thanks for filing this bug and linking to the other EFI related one. They
aren't the same.
This looks like a bug in curtin's remove duplicate code:
Removing duplicate EFI entry (0006, {'name': 'EFI Network 1', 'path':
> This commit adds VROC container and array creation (on clean disks)
> https://github.com/gyurco/curtin/commit/fd72c17665c071cde3eb5e047662b04ab993a0dd
Nice!
Now here's the not so fun part. We've not yet moved curtin to github, so code
submissions are done here:
> I think your suggestion is a good YAML scheme. I think size_kb:
> should be optional to fill the whole array with one volume if
> it's omitted.
Well, it's not that simple. What do we do if it's omitted and
the config includes multiple volumes from the same container?
Curtin config is
> 1-2) No, only the md-device, the container, raid level and number of
devices (it's possible to create different RAID volumes with different
levels in one container, however the number of devices must be the same
in all).
OK.
Looking at the
Cool!
The first step is to understand what additional metadata is needed to
construct an VROC device (this container).
The existing storage config yaml for raid looks like this:
https://curtin.readthedocs.io/en/latest/topics/storage.html#raid-command
It looks like we need to have a default
Thanks.
I won't mark this as a duplicate yet without further confirmation.
Would you be interested in working on the feature? I don't have access
to any Intel VROC devices which makes it difficult to implement.
I don't believe QEMU or other virt platforms emulate Intel VROC devices;
one needs
Hello,
Thanks for filing the bug. Do you know if VROC is different feature
than RSTe? There's an existing feature request for that here:
https://bugs.launchpad.net/curtin/+bug/1790055
** Changed in: curtin (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
Public bug reported:
After ~72 hours, my Gnome desktop will be very slow.
In syslog I noticed that I get a bunch of these messages as the system
slows down:
/usr/lib/gdm3/gdm-x-session[13460]: (EE) client bug: timer event6
debounce short: scheduled expiry is in the past (-30ms), your system is
Curtin is collecting by-id links to disk to populate grub2 's debconf
value:
grub-pc grub-pc/install_devices
It's not clear to me (yet) if providing non persistent values (like
/dev/sda) will work with
/usr/lib/grub/grub-multi-install
Even if it accepts non-by-id values; it's possible that on
low installed centos images to reboot (LP: #1881011)
-- Ryan Harper Thu, 20 Aug 2020 09:10:33 -0500
** Changed in: curtin (Ubuntu Groovy)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tomorrow's Curtin daily:ppa should have this (and as you can see, other
fixes)
https://launchpad.net/~curtin-dev/+archive/ubuntu/daily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891608
Title:
** Also affects: curtin (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Focal)
** Also affects: curtin (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/1891608
Title:
openvswitch-switch isn't installed if netplan schema
Tomorrows Curtin daily:ppa should have this (and as you can see, other
fixes)
https://launchpad.net/~curtin-dev/+archive/ubuntu/daily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892242
Title:
Updated image is available:
% image-status maas3 | grep groovy
groovy amd64/ga-20.10/generic 20200819.1 squashfs
groovy amd64/ga-20.10/lowlatency20200819.1 squashfs
GroovyTestBasic on amd64 passes.
Thu, 20 Aug 2020 09:40:51 -0500: vmtest start: nosetests3 -vv
Once a new maas image is published with the updated initramfs, I can
verify; As of today, I still only see 20200814 for groovy
% date
Wed 19 Aug 2020 11:03:04 AM CDT
% image-status maas3 | grep groovy
groovy amd64/ga-20.10/generic 20200814squashfs
groovy
https://code.launchpad.net/~raharper/cloud-initramfs-tools/+git/cloud-
initramfs-tools/+merge/389422
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890803
Title:
Groovy amd64 / arm64 / PowerPC
It turns out the 20200814 squashfs from maas *now* has an /etc/fstab in
it ...
So after overlayroot runs, we have an fstab like this:
root@(none):/# cat /etc/fstab
LABEL=cloudimg-rootfs /ext4 defaults0 0
#
# This fstab is for overlayroot. The real one can be found at
#
Thank you. I dont know how i did not see that before
On Mon, Aug 17, 2020 at 12:25 AM Daniel van Vugt <1891...@bugs.launchpad.net>
wrote:
> Also, please don't use Alt+F2. This command needs to be run in the
> Terminal app:
>
> journalctl -b-1 > prevboot.txt
>
> But only using the steps from
need a little more help than than. Im new to Ubuntu. I dont know how to
navigate
On Sun, Aug 16, 2020 at 11:55 PM Daniel van Vugt <1891...@bugs.launchpad.net>
wrote:
> The file should be created in the directory you ran the command so look
> there:
>
> journalctl -b-1 > prevboot.txt
> ls
i am not recieving a text file when i run the command
what am i doing wrong?
alt+f2 to bring up command
i have rebooted, suspended, reproduced flicker, rebooted then entered
verbatim. No text file appears?
On Sun, Aug 16, 2020 at 10:40 PM Daniel van Vugt <1891...@bugs.launchpad.net>
wrote:
>
This has probably already been noticed, but in an attempt to simply get
my PI working somewhat the way i wanted, i changed my tunnel to run over
wlan0 instead of eth0 (they both connect back to the same network so
doesn't make a huge difference).
Tunnel and interfaces have been up for days, no
Public bug reported:
when computer is coming out of suspension mode, i get terrible screen
flickers. Only way i have worked around this is a reboot.
This video card is from sapphire
Nitro + SE 5700xt
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
msp3k is correct. The bug is in autofs-ldap, not in slapd. slapd is
correct to reject "caseExactMatch" since the attribute syntax is IA5
String. The correct fix is what msp3k said, fix the matching rule to be
caseExactIA5Match like it was in the old one.
--- /etc/ldap/schema/autofs.schema
Public bug reported:
cant install
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Forgot to include:
Jul 28 18:18:25 dns1 kernel: [ 1289.970276] [ cut here ]
Jul 28 18:18:25 dns1 kernel: [ 1289.970354] NETDEV WATCHDOG: eth0 (lan78xx):
transmit queue 0 timed out
Jul 28 18:18:25 dns1 kernel: [ 1289.970463] WARNING: CPU: 1 PID: 0 at
I can confirm I am also seeing a very similar set of circumstances:
-Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT)
-5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 aarch64 aarch64
aarch64 GNU/Linux
-The "tunnel" in my case is using Wireguard to a server hosted externally.
FWIW, i actually thought this was a bug with the latest raspbian image
and decided to move forward with using 20.04 on my raspberry pi's, turns
out that wasn't the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Still there in groovy.
xsession-edit/groovy 0.5.3-2ubuntu1 amd64
configure what application start up automaticlly in LXDE
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085355
Title:
Typo in
It doesn't appear that this was ever accepted upstream. Sent email
requesting an upload of the patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206624
Title:
Typo in a fortune
To manage
This has been resolved.
ryan@ryan-Virtual-Machine:~$ grep "Section B" mutt-1.14.5/contrib/smime.rc
# Section B: Outgoing messages
** Changed in: mutt (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubunt
101 - 200 of 9903 matches
Mail list logo
